feat: support release stream baselines#15
Merged
Conversation
Bundle Size ReportCompared current build against latest npm release
Historical comparison: latest + 10 previous npm releases
|
There was a problem hiding this comment.
2 issues found across 21 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
There was a problem hiding this comment.
1 issue found across 10 files (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
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.
Summary
Tests
Summary by cubic
Adds optional
release-streaminput to select baselines from a specific major stream (e.g., 1.x) instead of npm latest. Reports, PR comments, and outputs now reflect the chosen stream; default behavior is unchanged.New Features
release-stream(major number). Primary baseline is newest stable in that stream; history stays within the stream. Default still uses npmlatest.releaseStream; PR comment baseline and history labels identify the stream; action outputs/README say “selected primary release.” Errors/logs now say “primary release.”dist;.gitattributesmarks generated and archived files; version bumped to0.1.1.Migration
release-stream: '1'(compares against1.x).Written for commit b9469f4. Summary will update on new commits. Review in cubic