Repository navigation
Conversation
github-actions
Bot
requested review from
craigcarlyle
and removed request for
a team
November 9, 2026 03:56
Member
|
I am skipping a review on this PR. Feel free to request a Doister's review if needed. |
craigcarlyle
approved these changes
Nov 9, 2026
github-actions
Bot
force-pushed
the
release-please--branches--main--components--react-compiler-tracker
branch
from
November 10, 2026 03:56
43dc35a to
fd79670
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main--components--react-compiler-tracker
branch
from
November 11, 2026 03:58
fd79670 to
5d31b1c
Compare
henningmu
added a commit
that referenced
this pull request
Nov 11, 2026
[Posted by Jarvis] Migrate the GitHub owner and package scope to `todoist`, preserving the `react-compiler-tracker` executable and Release Please tag lineage. The first new-scope release is **3.0.5**, through existing release PR #234; source and manifest remain 3.0.4 here. The dependency gate is resolved: `@todoist/tsconfig@2.0.2` is published on npm and its private GitHub mirror with matching integrity. This PR now includes the real registry lockfile and main's minimatch 11.0.5 patch. Node is pinned to 22.23.4 to satisfy the installed development dependency engine floor. Release Please creates the normal release record and dispatches pack-only at its exact tag. Publication reuses the retained artifact, validates the original successful run attempt, artifact ID/API digest and reviewed source ancestry, and checks both registries before any write. Missing mirrors preserve original bytes and cannot downgrade latest. Cross-run npm provenance is disabled. The npm package is public; the GitHub mirror remains private. Missing GitHub versions require readable package metadata; first-mirror absence requires active organization-owner evidence with the same credential. First publication uses the documented local owner path. Future workflow publication requires the protected `package-release` environment and npm trusted-publisher setup. Validation on Node 22.23.4 / npm 11.21.2: - Real registry lock generation and clean install, without lifecycle scripts. - TypeScript/Biome checks, all 78 product tests, and build passed. - All 18 release safety tests passed, including original-attempt recovery and hidden-package 404 guards. - Actionlint and whitespace checks passed; only the existing Biome schema informational notice remains. - Fresh read-only review found no unresolved code blockers; its first-mirror runbook correction is included. Push/PR effects were rechecked: source/title checks and doistbot only; no branch publication. Merging this PR updates the normal release PR. Merging #234 creates its standard tag/release and pack artifact; registry publication is a separate authorized step. See [the release runbook](docs/releasing.md).
github-actions
Bot
force-pushed
the
release-please--branches--main--components--react-compiler-tracker
branch
from
November 11, 2026 11:15
5d31b1c to
4fe125d
Compare
henningmu
deleted the
release-please--branches--main--components--react-compiler-tracker
branch
November 11, 2026 11:17
Contributor
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
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.
[Posted by Jarvis]
🤖 I have created a release beep boop
3.0.5 (2026-11-11)
Bug Fixes
This PR was generated with Release Please. See documentation.