Skip to content

chore: update expired @lunariajs/core pkg.pr.new package #1560

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
danielroe merged 1 commit into from
Feb 22, 2026
Merged

chore: update expired @lunariajs/core pkg.pr.new package #1560

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@
"@iconify-json/svg-spinners": "1.2.4",
"@iconify-json/vscode-icons": "1.2.40",
"@intlify/shared": "11.2.8",
"@lunariajs/core": "https://pkg.pr.new/lunariajs/lunaria/@lunariajs/core@f07e1a3",
"@lunariajs/core": "https://pkg.pr.new/lunariajs/lunaria/@lunariajs/core@904b935",
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

pkg.pr.new package expiry policy temporary registry

💡 Result:

pkg.pr.new is explicitly a temporary, npm-compatible preview registry, not a permanent package host. (blog.stackblitz.com)

From the published infrastructure notes on its storage management:

  • Inactive cleanup: preview packages that are at least 1 month old and haven’t been downloaded in over 1 month are automatically removed. (gist.github.com)
  • Hard max age: any preview package older than 6 months is removed, even if it’s still being downloaded. (gist.github.com)

Citations:

🌐 Web query:

pnpm github git dependency syntax package.json

💡 Result:

pnpm supports the standard npm “git dependency” spec in package.json, including GitHub shorthands.

GitHub shorthand (most common)

{
  "dependencies": {
    "my-lib": "user/repo",
    "my-lib-commit": "user/repo#97edff6f525f192a3f83cea1944765f769ae2678",
    "my-lib-branch": "user/repo#master",
    "my-lib-semver-tags": "user/repo#semver:^2.0.0"
  }
}

pnpm documents the same forms via pnpm add (commit / branch / #semver:). [1]

Explicit github: (equivalent style)

{
  "dependencies": {
    "my-lib": "github:user/repo#HEAD"
  }
}

npm’s package spec documents github:user/repo#ref and user/repo#ref as valid git shorthands. [2]

Full git URLs (HTTPS/SSH) + ref

{
  "dependencies": {
    "my-lib-https": "git+https://github.com/user/repo.git#v1.2.3",
    "my-lib-ssh": "git+ssh://git@github.com/user/repo.git#v1.2.3"
  }
}

This is the canonical “git URL as dependency” form per npm’s package spec. [2]

Notes

  • The part after # can be a tag, branch, or commit SHA; #semver:<range> selects a matching tag/ref (when available). [1][2][3]
  • You can also do this from the CLI and let pnpm write it: pnpm add github:user/repo#<ref>. [1]

Sources: pnpm add docs [1], npm package spec (git URLs & GitHub shorthands) [2], pnpm Git install examples (#commit, #branch, #semver) [3].

🌐 Web query:

@lunariajs/core v1 release npm stable version

💡 Result:

As of the latest npm publish information available, @lunariajs/core does not have a v1.x stable release. The current stable (“latest”) version on npm is 0.1.1. [1]

Lunaria’s own announcement also frames the project’s first public release as v0.1, indicating it’s still pre-1.0. [2]

Sources: [1], [2]

pkg.pr.new references are ephemeral — this will expire again.

pkg.pr.new publishes unreleased packages to a temporary npm-compatible preview registry. Packages are automatically removed if they're at least 1 month old and haven't been downloaded in over a month, or if they exceed 6 months old regardless of download activity. This PR swaps one expired commit hash for another, but the new reference (904b935) will expire under exactly the same conditions, causing the same deploy failure to recur.

Consider switching to a non-expiring alternative until @lunariajs/core v1 lands on npm as a stable release:

♻️ Suggested alternative: git dependency (does not expire) 
-    "@lunariajs/core": "https://pkg.pr.new/lunariajs/lunaria/@lunariajs/core@904b935",
+    "@lunariajs/core": "github:lunariajs/lunaria#904b935",

Once the v1 branch publishes a stable release to the npm registry, migrate to a pinned semver version (e.g. "@lunariajs/core": "^1.0.0") to eliminate this class of breakage entirely.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"@lunariajs/core": "https://pkg.pr.new/lunariajs/lunaria/@lunariajs/core@904b935",
"@lunariajs/core": "github:lunariajs/lunaria#904b935",

"@napi-rs/canvas": "0.1.92",
"@nuxt/a11y": "1.0.0-alpha.1",
"@nuxt/fonts": "0.13.0",
Expand Down
10 changes: 5 additions & 5 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading