chore: version packages - #15
Merged
Merged
Conversation
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@murky-web/simplelog@2.0.1
Patch Changes
c924b3f: Fix
@murky-web/simplelog/otel, which threw on import in 2.0.0.dist/otel.jsimportedsetSpanContextReaderfromdist/logger_factory.js, andthat file did not export it:
The build runs two tsdown config blocks — one
platform: "node", oneplatform: "neutral"— that write to the sameoutDir.logger_factorywas anentry in neither, so each block emitted it keeping only the exports its own
entries used, and the block that finished last decided the file. The neutral
block's entries (
deno,hono,web) never callsetSpanContextReader, sowhen it won, the export was gone. The order is not fixed: rebuilding the broken
config five times produced a working file once and a broken one four times,
which is how this reached npm.
Naming
logger_factoryas an entry in both blocks preserves its full exportsurface either way. Verified stable across repeated builds.
A new
smoke:entriescheck imports every subpath in theexportsmap from thebuilt output and fails if one does not load or exports nothing. It runs as part
of
release:verify:simplelog. Nothing existing could have caught this: lint andtypecheck read the source, and the generated
otel.d.tsdescribed the exportthat the JavaScript was missing — only loading the built files reveals it.