feat: show staged publishing status - #3115
BittuBarnwal7479 wants to merge 4 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (5)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe package metadata model now exposes staged-publishing trust status. Package headers, version lists, and version pages render a reusable staged-publishing badge with translated text and npm documentation links. ChangesStaged publish visibility
Sequence Diagram(s)sequenceDiagram
participant PackageMetadata
participant PackageViews
participant StagedPublishBadge
participant NpmDocumentation
PackageMetadata->>PackageViews: provide trustStatus.stagedPublish
PackageViews->>StagedPublishBadge: render badge
StagedPublishBadge->>NpmDocumentation: open documentation link
Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to Requested historical package versions retain their staged-publishing and provenance metadata for badge rendering. No concrete merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (3 passed)
Full details: Out of Scope Changes checkExplanation
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
e18e dependency analysisNo dependency warnings found. |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@app/components/Package/Versions.vue`:
- Line 644: Update every StagedPublishBadge occurrence identified in this diff,
including the instances near the current row and the additional listed
locations, to include the relative z-10 classes so the badge remains above the
full-row link hit target and its documentation links stay clickable.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 73d03b63-4e54-4481-bdd8-9834008f4b8d
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (11)
app/components/Package/Header.vueapp/components/Package/Versions.vueapp/components/StagedPublishBadge.vueapp/pages/package/[[org]]/[name]/versions.vueapp/utils/npm/api.tsi18n/locales/en.jsoni18n/schema.jsonpackage.jsonshared/types/npm-registry.tstest/nuxt/components/Package/Versions.spec.tstest/nuxt/composables/use-package-transform.spec.ts
ghostdevv
left a comment
There was a problem hiding this comment.
I think that we should show this information in the timeline, as well as the notices on the package homepage that show when a package now has staged publishing. We could also show it in the versions list maybe with an additional badge alongside provenance - wdyt @gameroman?
(This might make sense to do over multiple PRs)
Yeah, I think we can add it to the timeline in a separate PR |
yep, you’re right. Adding staged publishing information to the timeline is outside the focused scope of this issue. If it sounds good to the other reviewers, I can open a separate PR for it. thanks for review! |
Thanks for opening this pull request! 🎉We really appreciate you taking the time to contribute, @BittuBarnwal7479. A maintainer will take a look as soon as they can. In the meantime, please make sure that:
If anything needs adjusting we'll leave comments here. Thanks again! |
6d5d307 to
0ac6c3c
Compare

🔗 Linked issue
fixes: #3114
🧭 Context
📚 Description
Adds a linked indicator for package versions published through npm’s staged publishing flow. Also updates version metadata handling and adds test coverage.
Recording.2026-08-03.055544.mp4