chore(release): cut ui-kit v1.1.3#8506
Closed
JSONbored wants to merge 2 commits into
Closed
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | 542f2b3 | Commit Preview URL Branch Preview URL |
Jul 24 2026, 04:01 PM |
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
loopover-orb
Bot
added
the
gittensor:bug
Contributor
|
Note LoopOver command help
Command: Command resultCommands
Findings
Evidence
Next actions
Source and freshness
Additional safe details
Feedback
💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers. |
Bundle ReportChanges will increase total bundle size by 104 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: loopover-uiAssets Changed:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8506 +/- ##
===========================================
+ Coverage 81.11% 92.53% +11.41%
===========================================
Files 791 793 +2
Lines 79344 79487 +143
Branches 23967 24019 +52
===========================================
+ Hits 64360 73551 +9191
+ Misses 12133 4799 -7334
+ Partials 2851 1137 -1714
Flags with carried forward coverage won't be shown. Click here to find out more. |
Owner
Author
|
Closing as superseded: the reconcile self-heal created the ui-kit-v1.1.2 tag today at d09fbe2 (main head at the time) rather than the v1.1.2 release PR's merge commit, which swept ddb674e (the react-hook-form dependency fix — the only content this v1.1.3 PR proposed) into the published 1.1.2. Verified: npm's @loopover/ui-kit@1.1.2 declares react-hook-form ^7.80.0. With nothing left to release, release-please skips the component ('No commits for path') and never regenerates or prunes this branch, so the manifest conflict could never self-heal. release-please will cut a fresh release PR on the next ui-kit commit. |
This was referenced Jul 24, 2026
Open
JSONbored
added a commit
that referenced
this pull request
Jul 24, 2026
…patch head (#8527) Advances #8525. The reconcile self-heal dispatches publish-*.yml bare (against main head), and the bare-dispatch path tagged-and-packed HEAD -- during today's runner backlog that placed ui-kit-v1.1.2 two commits late, sweeping the would-be 1.1.3 fix into the 1.1.2 tag and published artifact and zombifying the open v1.1.3 release PR (release-please saw 'No commits for path' behind the misplaced tag and could neither regenerate nor prune it; closed by hand as #8506). All four publish workflows now resolve the RELEASE COMMIT -- the newest main commit that introduced the current version string into the package's own package.json (the release PR's merge commit) -- then: - verify it is reachable from main, - verify any pre-existing tag points AT it (not at HEAD), - detach onto it so typecheck/pack build the exact tree the version number describes, - create the annotated tag at it explicitly. Unresolvable ⇒ hard abort, never a head fallback. The release-please dispatch path (dispatched against the tag itself) is byte-identical in effect: there HEAD already IS the release commit. Regression pins in test/unit/publish-release-tag-pins.test.ts cover the resolver, the fail-loud arm, the detach, and the death of every head-tagging form across all four workflows.
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.1.3 (2026-07-24)
Fixes
This PR was generated with Release Please. See documentation.