release 0.6.0 - #35
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.
Cuts 0.6.0, a minor release.
What's new
RemoteConfig.autoConnect(boolean, defaulttrue). Setfalseto skip the broker connect oninitialize()and drive it yourself viareconnect(url, ticket)— the pattern for dynamically-minted-per-connection JWTs, avoiding the ticketless startup probe an auth-requiring broker rejects once per page load.@laboverwire/stitch-wasmfloor^0.2.2 → ^0.3.0(0.3.0 implementsremote.autoConnect).Additive and non-breaking — default
autoConnect: truepreserves existing behavior. Minor bump because it adds a public config field.Contents
package.json: 0.5.1 → 0.6.0CHANGELOG.md:## 0.6.0section + fresh empty## UnreleasedVerification
npm run release:checkpasses: type-check, lint, format, 35 tests, changelog gate all green.extract-changelog.mjs 0.6.0produces the release notes the publish workflow will use.Release
After merge, tagging
v0.6.0on the merge commit triggersrelease.yml→ verify tag == version → check → build → npm publish --provenance → GitHub Release.