Chore/deps 09 11 25 #313
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| --- | ||
| '@lglab/react-qr-code': patch | ||
| 'reactqrcode.com': patch | ||
| --- | ||
|
|
||
| chore(deps) |
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,23 +1,24 @@ | ||
| import { defineConfig, globalIgnores } from 'eslint/config'; | ||
| import nextVitals from 'eslint-config-next/core-web-vitals'; | ||
| import nextTs from 'eslint-config-next/typescript'; | ||
|
|
||
| const eslintConfig = defineConfig([ | ||
| ...nextVitals, | ||
| ...nextTs, | ||
| // Override default ignores of eslint-config-next. | ||
| globalIgnores([ | ||
| // Default ignores of eslint-config-next: | ||
| '.next/**', | ||
| 'out/**', | ||
| 'build/**', | ||
| 'next-env.d.ts', | ||
| ]), | ||
| { | ||
| rules: { | ||
| '@typescript-eslint/consistent-type-imports': 'error', | ||
| 'no-console': 'error', | ||
| }, | ||
| }, | ||
| ]); | ||
|
|
||
| export default eslintConfig; |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,6 @@ | ||
| /// <reference types="next" /> | ||
| /// <reference types="next/image-types/global" /> | ||
| import './.next/dev/types/routes.d.ts' | ||
|
|
||
| // NOTE: This file should not be edited | ||
| // see https://nextjs.org/docs/app/api-reference/config/typescript for more information. |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify npm publishing configuration after removing authentication tokens.
The addition of
id-token: writepermission alongside removal ofNPM_TOKENandNODE_AUTH_TOKENsuggests a migration to npm provenance/trusted publishing. Ensure that:GITHUB_TOKENhas been granted npm registry access🏁 Script executed:
Length of output: 55
Length of output: 556
Length of output: 71
💡 Result:
Short summary (2024 status + what changed afterward):
Sources
Restore
NPM_TOKEN— pnpm does not yet support OIDC/trusted publishing.pnpm as of mid-2025 does not implement OIDC/trusted publishing; an open feature request exists but remains unimplemented. The removal of
NPM_TOKENandNODE_AUTH_TOKENwithout an alternative authentication method will causepnpm publishto fail.Restore
NPM_TOKENto theenvsection (line 47) until pnpm adds OIDC support, or migrate to npm/yarn if OIDC-based publishing is required.🤖 Prompt for AI Agents