chore(release): 2.1.0#27
Merged
Merged
Conversation
ashleythedeveloper
force-pushed
the
release/2.1.0
branch
from
31b2c6b to
9715eee
Compare
Contributor
Code Coverage Report
|
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
1 participant
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.
First release under the trunk-based, tag-triggered model from #26. Bumps
package.jsonto2.1.0and adds the correspondingCHANGELOG.mdandRELEASE_NOTES.mdentries for the digest-multibase helpers.Once #26 is merged, this PR retargets onto
main. After merging, pushingv2.1.0will trigger the newReleaseworkflow to publish to npm.The two
feat(render-method-2024)commits are cherry-picks of the work previously reviewed and merged via #25; they bring the digest helpers onto the new trunk.Test plan
yarnchecks pass locally (lint, format, test, build)scripts/check-tag-version-match.mjsacceptsv2.1.0against the newpackage.jsonReleaseworkflow runs, the version-match guard passes, and the npm publish via OIDC succeeds