Repository navigation
chore(release): 0.10.0-next.1 - #131
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
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.
Pre-release for testing opencode v2 support. Bumps to 0.10.0-next.1 and cuts the CHANGELOG section.
0.10.0-next.0was tagged but never published (release job failed at the npm publish step, see #130), so this is the first published build with v2 support and includes the #129 provider-version pin. Adds a note that users behind a registry mirror can hitETARGETon a fresh pre-release, because v2 now installs the provider at exactly the plugin's version.Merge order: #130 first (fixes the publish path), then this, then tag
v0.10.0-next.1on the merge commit.