fix(*): align remaining types and publish runtime follow-up#671
Merged
mttrbrts merged 1 commit intoMay 10, 2026
Conversation
Signed-off-by: Rishabh Jain <rishabhj2005@gmail.com>
mttrbrts
approved these changes
May 10, 2026
7af1052
into
accordproject:feat/tighten-typescript-types
2 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #669
This PR is a focused follow-up on top of #669 to address the remaining gaps found during review.
Changes
.github/workflows/publish.ymlto use Node 22 so the release workflow matches the newengines.node >=22requirement introduced in feat: tighten TypeScript type declarations — replaceanywith concrete types #669HtmlTransformerto emitHtmlInput/IDocumentandTemplateMarkTransformer.getSerializer()to emitSerializerFlags
feat/tighten-typescript-typesso the diff stays limited to the follow-up fixes instead of duplicating feat: tighten TypeScript type declarations — replaceanywith concrete types #669packages/markdown-templatestill has the existingno-consolelint warnings in its source, but this follow-up does not introduce any new lint errorsScreenshots or Video
Related Issues
anywith Concerto model types #668anywith concrete types #669Author Checklist
--signoffoption of git commit.feat/tighten-typescript-typesfromRishabh060105/pr669-followup-fixesValidation
npm run build --workspace packages/markdown-templatenpm run build --workspace packages/markdown-htmlnpm run lint --workspace packages/markdown-templatenpm run lint --workspace packages/markdown-htmlnpm test --workspace packages/markdown-templatenpm test --workspace packages/markdown-html