chore: release v0.7.10#1734
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
miguel-heygen
temporarily deployed
to
npm-publish
GitHub Actions
Inactive
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.
What
Bumps all HyperFrames publishable packages and plugin manifests to
0.7.10, with reviewed release notes for the two producer fixes included in this stable cut.Why
0.7.10ships the distributed-render root fix that rejects impossible probed durations before chunk fanout, plus the distributed frame-path indexing fix from #1730. Publishing this stable version giveshyperframes-internala versioned package set to consume for the next producer-internal deployment.How
Ran the canonical release flow on
release/v0.7.10: drafted/reviewed the changelog, reranrelease:prepare, and let the script update package/plugin versions and create the release commit. The localv0.7.10tag was not pushed; the publish workflow will create/push the tag when thisrelease/v0.7.10PR merges.Test plan
Verification run:
PATH="/tmp/node22-bin:$PATH" bun run release:prepare 0.7.10PATH="/tmp/node22-bin:$PATH" bun run format:checkPATH="/tmp/node22-bin:$PATH" bun run test:scriptsVERSION=0.7.10 DIST_TAG=latest EVENT_NAME=pull_request PR_HEAD_REF=release/v0.7.10 PATH="/tmp/node22-bin:$PATH" bun run validate:release-channel