chore(release): cut ui-kit v1.7.0 - #10283
Merged
JSONbored merged 4 commits intoAug 2, 2026
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | 23050b3 | Commit Preview URL Branch Preview URL |
Aug 02 2026, 12:44 AM |
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Bundle ReportBundle size has no change ✅ |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #10283 +/- ##
=======================================
Coverage 92.31% 92.31%
=======================================
Files 939 939
Lines 114816 114816
Branches 27729 27729
=======================================
Hits 105989 105989
Misses 7527 7527
Partials 1300 1300
Flags with carried forward coverage won't be shown. Click here to find out more. |
…e manifest/lock conflict # Conflicts: # .release-please-manifest.json
This was referenced Aug 2, 2026
Closed
JSONbored
added a commit
that referenced
this pull request
Aug 2, 2026
…elease commit (#10287) publishedSourcePrefixes includes <pkg>/package.json, and a release-please release commit is `chore(release): …` whose entire job is to write the new version into exactly that file. So the guard matched by construction on every release PR it ever ran against -- #10283 surfaced it, where the flagged claim ("would merge green and then never reach npm") is exactly backwards: that commit is the one that performs the release, and a maintainer cannot reword it because release-please generates it. This file's own isPublishedFile note already warns that a guard firing on the ordinary case is a guard that gets disabled. The exemption keys on what the diff DID, not on the subject: a commit borrowing the `chore(release):` subject while editing a dependency range or an exports map still strands a real change, so only a manifest whose sole changed lines are the "version" field is dropped. A commit left with no other published-source path is release-please's own and is not stranded; a mixed commit still reports its remaining paths. An empty diff proves nothing and stays flagged, which keeps the default accessor's behaviour unchanged. Closes #10286
JSONbored
deleted the
release-please--branches--main--components--ui-kit
branch
August 2, 2026 01:49
Owner
Author
|
🤖 Created releases: 🌻 |
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.
🤖 I have created a release beep boop
1.7.0 (2026-07-31)
Features
Fixes
Dependencies
This PR was generated with Release Please. See documentation.