Version core 0.8.1 as the release anchor - #31
Merged
Merged
Conversation
The npm release is triggered by a v* tag whose version has to match this package, and the environment that publishes accepts no other ref, so the connectors, server, mcp, react and the widget cannot be published while this version stands still. The widget is the one that needs it: it bundles the engine, so the fix reaches its users only when it is published. No source changed since 0.8.0.
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.
The npm release is triggered by a
v*tag whose version must match@asksql/core, and thenpm-publishenvironment accepts no other ref - aworkflow_dispatchonmainis rejected before any step runs. So the nine patch bumps merged in #30 cannot publish while core stands at 0.8.0, which is already on the registry.Core moves to 0.8.1 as the anchor. No source changed since 0.8.0; the widget is the package that actually needs the republish, because it bundles the engine and reaches its users only when published.
Verified:
pnpm verifyexit 0, frozen lockfile clean.