Repository navigation
chore: release v0.4.0 - #188
Merged
Merged
Conversation
Signed-off-by: Bart Waardenburg <bart@waardenburg.dev>
The codec and sourcemap packages list their platform packages as exact optionalDependencies. The lockfile resolved them from npm. A version bump then needs a version that npm does not have yet, so the frozen install in CI and in the release workflow fails. Add the platform package folders to the workspace. pnpm now links them locally, and the lockfile does not depend on a published version. Signed-off-by: Bart Waardenburg <bart@waardenburg.dev>
Merging this PR will not alter performance1 warning
Comparing Footnotes
|
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.
Bump all crates and npm packages from 0.3.9 to 0.4.0. Update the README install versions to "0.4".
This release includes the webpki-roots 1.0.10 update for RUSTSEC-2026-0381. The minor bump marks two changes that can break callers:
SourceMap.source()andSourceMap.name()in@srcmap/sourcemapnow declarestring | null.The second commit fixes the release process. The platform packages were exact
optionalDependenciesthat the lockfile resolved from npm. Version 0.4.0 is not on npm before the release, sopnpm install --frozen-lockfilefailed in CI and would fail in the release workflow. The platform package folders are now workspace members, so pnpm links them locally.