react-hackernews
react-hackernews copied to clipboard
chore(deps): update dependency @commitlint/cli to v19
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @commitlint/cli (source) | ^18.6.1 -> ^19.3.0 |
Release Notes
conventional-changelog/commitlint (@commitlint/cli)
v19.3.0
Note: Version bump only for package @commitlint/cli
19.2.2 (2024-04-14)
Note: Version bump only for package @commitlint/cli
19.2.1 (2024-03-19)
Note: Version bump only for package @commitlint/cli
v19.2.2
Note: Version bump only for package @commitlint/cli
v19.2.1
Note: Version bump only for package @commitlint/cli
v19.2.0
Features
v19.1.0
Note: Version bump only for package @commitlint/cli
19.0.3 (2024-02-28)
Note: Version bump only for package @commitlint/cli
19.0.2 (2024-02-28)
Note: Version bump only for package @commitlint/cli
19.0.1 (2024-02-27)
Bug Fixes
- drop
resolve-from,resolve-globalandimport-fresh, resolve global packages correctly (#3939) (8793c63), closes #3938
v19.0.3
Note: Version bump only for package @commitlint/cli
v19.0.2
Note: Version bump only for package @commitlint/cli
v19.0.1
Bug Fixes
- drop
resolve-from,resolve-globalandimport-fresh, resolve global packages correctly (#3939) (8793c63), closes #3938
v19.0.0
Reverts
- Revert "chore!: minimum node version v20" (2816783)
BREAKING CHANGES
-
migrate to pure ESM
-
feat: migrate to pure ESM
-
chore: update snapshot
-
fix: load
parserPresetwith anotherawait -
test: migrate to vitest
-
test: remove no replacement
--runInBandtest-ci script -
chore: fix code reviews
-
refactor(load): rewrite resolve logic
-
fix(config-nx-scopes): fix syntax error
-
feat(resolve-extends): add resolveFrom and loadParserPreset
-
feat(load): use resolveFrom and loadParserPreset from resolve-extends
-
test: include only @commitlint/* packages src in coverage
-
test: explicit import vitest utilities
-
test: remove @jest/globals from dependencies
-
fix(resolve-extends):
resolveFromoutput should be platform aware -
test: restore NO_COLOR to test script
-
chore: fix linting issues
-
fix: should use fileURLToPath instead of pathname for Windows compatibility
-
Apply suggestions from code review
-
fix: should reuse
cliinstead callyargs() -
feat(cli): set terminalWidth as wrap to avoid work break on help
-
Update .eslintrc.cjs
-
feat: migrate @commitlint/config-conventional to pure ESM
18.6.1 (2024-02-13)
Note: Version bump only for package @commitlint/cli
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: yarn.lock
/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23250
const isURL = URL.canParse(range);
^
TypeError: URL.canParse is not a function
at parseSpec (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23250:21)
at loadSpec (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23313:11)
at async Engine.findProjectSpec (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23487:22)
at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23539:24)
at async Object.runMain (/opt/containerbase/tools/corepack/0.28.0/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:24232:5)
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| react-hackernews | ❌ Failed (Inspect) | Aug 7, 2024 9:38am |
⚠️ No Changeset found
Latest commit: dc5a53e4fa9f8a5a17563de7457580ed78ad5970
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: yarn.lock
/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21609
throw new Error(
^
Error: Error when performing the request to https://registry.npmjs.org/yarn/latest; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
at fetch (/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21609:11)
at async fetchAsJson (/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21623:20)
... 4 lines matching cause stack trace ...
at async Object.runMain (/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23096:5) {
[cause]: TypeError: globalThis.fetch is not a function
at fetch (/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21603:33)
at async fetchAsJson (/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21623:20)
at async fetchLatestStableVersion (/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21550:20)
at async fetchLatestStableVersion2 (/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:21672:14)
at async Engine.getDefaultVersion (/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22292:23)
at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:22390:47)
at async Object.runMain (/opt/containerbase/tools/corepack/0.29.3/16.20.2/node_modules/corepack/dist/lib/corepack.cjs:23096:5)
}
Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 19.x releases. But if you manually upgrade to 19.x then Renovate will re-enable minor and patch updates automatically.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.