chore(deps): install openframe-frontend-core from pkg.pr.new (0.0.697) - #536
Open
michaelassraf wants to merge 2 commits into
Open
michaelassraf wants to merge 2 commits into
michaelassraf wants to merge 2 commits into
Conversation
… to 0.0.697) [preview:none] Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
🦩 Flamingo Code Review1 finding(s) — 1 action required · 0 recommended · 0 informational Mode: advisory · 1 defect(s) outside any rule Inline comments: 1 new Need another pass? Commits pushed after this review are not reviewed automatically.
Prefer typing? Comment React 👍/👎 on inline comments to teach the reviewer. Started 2026-10-04 01:26 UTC · updated 2026-10-04 01:26 UTC · workflow run |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Installs
@flamingo-stack/openframe-frontend-corefrom pkg.pr.new instead of npmjs, and moves it from0.0.694to0.0.697.Why. Since 2026-07 npm scans every upload before serving it, so a new lib release is not installable for minutes to hours after it is published (
0.0.695took 85 minutes,0.0.696almost two hours). The lib now publishes every build to pkg.pr.new as well (flamingo-stack/openframe-oss-lib#2524, #2525), where a release is installable the moment its run ends, with no token.multi-platform-hubmade the same switch in flamingo-stack/multi-platform-hub#1502.Change.
package.json: the pin becomes the release's pkg.pr.new URL, named by its version:https://pkg.pr.new/flamingo-stack/openframe-oss-lib/@flamingo-stack/openframe-frontend-core@0.0.697package-lock.json: the lib's entry now resolves to that URL with its integrity hash (8 lines; nothing else moved), sonpm ciinstalls exactly these bytes.There is no pkg.pr.new build of
0.0.694, so the switch comes with the lib bump to0.0.697.To bump later: change the version at the end of the URL and run
npm install --package-lock-only.To know. pkg.pr.new removes a build after six months, or after one month with no downloads; a pin is expected to move forward.
Checked locally.
npm cifrom the new lockfile installs lib0.0.697;npm run type-checkpasses. Lint, tests and the build are left to this PR's checks.Change-Set: chore-lib-pkg-pr-new-consumers
🤖 Generated with Claude Code
Change set
flamingo-stack/openframe-oss-frontend#536: these pull requests are one change, reviewed together.Merge order: #536 → flamingo-stack/openframe-oss-lib#2526
Linked by the
Depends-On/Change-Setlines in these descriptions; this block is maintained by the hub.