latipun7/library

Nerdy Ninja's library 🥷📜

library's Issues

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: .github/renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid configuration option: packageRules[0].matchManagers, Invalid configuration option: packageRules[0].matchPackageNames, Invalid configuration option: packageRules[1].extractVersion, Invalid configuration option: packageRules[1].matchDepTypes, Invalid configuration option: packageRules[2].matchPackageNames, Invalid configuration option: packageRules[2].matchPackagePatterns, Invalid configuration option: packageRules[3].matchPackageNames, Invalid configuration option: packageRules[3].matchPackagePatterns, Invalid configuration option: packageRules[4].matchPackagePatterns, Invalid configuration option: packageRules[5].matchDepTypes, Invalid configuration option: packageRules[6].matchDepTypes, Invalid configuration option: packageRules[7].automergeStrategy, Invalid configuration option: packageRules[7].matchPackagePrefixes, Invalid configuration option: packageRules[8].matchDepTypes, Regex Manager contains disallowed fields: description, packageRules: Each packageRule must contain at least one selector (paths, languages, baseBranchList, managers, datasources, depTypeList, packageNames, packagePatterns, excludePackageNames, excludePackagePatterns, sourceUrlPrefixes, updateTypes). If you wish for configuration to apply to all packages, it is not necessary to place it inside a packageRule at all., packageRules: Each packageRule must contain at least one selector (paths, languages, baseBranchList, managers, datasources, depTypeList, packageNames, packagePatterns, excludePackageNames, excludePackagePatterns, sourceUrlPrefixes, updateTypes). If you wish for configuration to apply to all packages, it is not necessary to place it inside a packageRule at all., packageRules: Each packageRule must contain at least one selector (paths, languages, baseBranchList, managers, datasources, depTypeList, packageNames, packagePatterns, excludePackageNames, excludePackagePatterns, sourceUrlPrefixes, updateTypes). If you wish for configuration to apply to all packages, it is not necessary to place it inside a packageRule at all., packageRules: Each packageRule must contain at least one selector (paths, languages, baseBranchList, managers, datasources, depTypeList, packageNames, packagePatterns, excludePackageNames, excludePackagePatterns, sourceUrlPrefixes, updateTypes). If you wish for configuration to apply to all packages, it is not necessary to place it inside a packageRule at all., packageRules: Each packageRule must contain at least one selector (paths, languages, baseBranchList, managers, datasources, depTypeList, packageNames, packagePatterns, excludePackageNames, excludePackagePatterns, sourceUrlPrefixes, updateTypes). If you wish for configuration to apply to all packages, it is not necessary to place it inside a packageRule at all., packageRules: Each packageRule must contain at least one selector (paths, languages, baseBranchList, managers, datasources, depTypeList, packageNames, packagePatterns, excludePackageNames, excludePackagePatterns, sourceUrlPrefixes, updateTypes). If you wish for configuration to apply to all packages, it is not necessary to place it inside a packageRule at all., packageRules: Each packageRule must contain at least one selector (paths, languages, baseBranchList, managers, datasources, depTypeList, packageNames, packagePatterns, excludePackageNames, excludePackagePatterns, sourceUrlPrefixes, updateTypes). If you wish for configuration to apply to all packages, it is not necessary to place it inside a packageRule at all., packageRules: Each packageRule must contain at least one selector (paths, languages, baseBranchList, managers, datasources, depTypeList, packageNames, packagePatterns, excludePackageNames, excludePackagePatterns, sourceUrlPrefixes, updateTypes). If you wish for configuration to apply to all packages, it is not necessary to place it inside a packageRule at all., packageRules: Each packageRule must contain at least one selector (paths, languages, baseBranchList, managers, datasources, depTypeList, packageNames, packagePatterns, excludePackageNames, excludePackagePatterns, sourceUrlPrefixes, updateTypes). If you wish for configuration to apply to all packages, it is not necessary to place it inside a packageRule at all.

Make all modules pure ESM 🚨

Motivation

NodeJS 10 LTS reached its End of Life while nodeJS 14 LTS and above support native ESM now.
More info read here.

Blocked by

• semantic-release/semantic-release#2054
• semantic-release/semantic-release#2133
• cosmiconfig/cosmiconfig#224
  (for cosmiconfig based shareable config, commitlint, eslint, etc)

(Optional) Another things for consideration

• NodeJS 14 and 16 ESM JSON Modules still experimental enabled by --experimental-json-modules flag.
• WASM too with --experimental-wasm-modules.
• Top level await still experimental too.

Adjustments

• nodejs/node#33460
  (no need to explicitly export package.json)

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• build(deps): replace read-pkg-up with read-package-up ^11.0.0
• build(deps): update semantic-release monorepo (@semantic-release/changelog, semantic-release)
• build(deps-dev): update @types/confusing-browser-globals to ^1.0.3
• build(deps-dev): update @types/conventional-changelog-writer to ^4.0.10
• build(deps-dev): update @types/semantic-release to ^17.2.11
• build(deps-dev): update semantic-release-monorepo to ^7.0.8
• build(deps): update eslint-import-resolver-typescript to ^2.7.1
• build(deps-dev): update commitizen to ^4.3.0
• build(deps-dev): update lint-staged to ^12.5.0
• build(deps-dev): update prettier to ^2.8.8
• build(yarn): update yarn to v3.8.1
• build(deps): update conventional-changelog-conventionalcommits to v7
• build(deps): update eslint-import-resolver-typescript to v3
• build(deps): update read-pkg-up to v11
• build(deps): update read-pkg to v9
• build(deps): update semantic-release-vsce to v5
• build(deps): update eslint packages (major) (@next/eslint-plugin-next, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint, eslint-config-prettier, eslint-plugin-jest, eslint-plugin-prettier, eslint-plugin-testing-library)
• build(deps-dev): update @types/semantic-release to v20
• build(deps-dev): update conventional-changelog-writer to v7
• build(deps-dev): update conventional-commits-parser to v5 (conventional-commits-parser, @types/conventional-commits-parser)
• build(deps-dev): update husky to v9
• build(deps-dev): update inquirer to v9
• build(deps-dev): update lint-staged to v15
• build(deps-dev): update prettier to v3
• build(deps-dev): update semantic-release-monorepo to v8
• build(deps-dev): update typescript to v5
• build(yarn): update yarn to v4
• chore(deps): update semantic-release to v23
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• build(deps-dev): update conventional-changelog-writer to ^5.0.1
• chore(deps): maintain lock-file

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• security(deps-tree): update semantic-release to v19 [security]
• build(deps-dev): update conventional-commits-parser to ^3.2.4 (conventional-commits-parser, @types/conventional-commits-parser)
• build(deps-dev): update inquirer to ^8.2.6
• build(deps): update eslint packages (@next/eslint-plugin-next, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint, eslint-config-prettier, eslint-plugin-import, eslint-plugin-jest, eslint-plugin-jsx-a11y, eslint-plugin-prettier, eslint-plugin-react, eslint-plugin-react-hooks, eslint-plugin-testing-library)
• build(deps-dev): update eslint-find-rules to ^4.1.0
• build(deps-dev): update typescript to ^4.9.5
• build(deps-dev): update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/cz-commitlint, @commitlint/types)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/ci-cd.yml

• styfle/cancel-workflow-action 0.9.1
• styfle/cancel-workflow-action 0.9.1

npm

configs/commitlint/package.json

• conventional-changelog-conventionalcommits ^4.6.3
• @commitlint/types ^15.0.0
• @commitlint/cli ^15.0
• @commitlint/cz-commitlint ^15.0
• commitizen ^4.2
• inquirer ^8.2

configs/eslint/package.json

• @next/eslint-plugin-next ^12.0.7
• @typescript-eslint/eslint-plugin ^5.6.0
• @typescript-eslint/parser ^5.6.0
• confusing-browser-globals ^1.0.11
• eslint-config-prettier ^8.3.0
• eslint-import-resolver-typescript ^2.5.0
• eslint-plugin-import ^2.25.3
• eslint-plugin-jest ^25.3.0
• eslint-plugin-jsx-a11y ^6.5.1
• eslint-plugin-prettier ^4.0.0
• eslint-plugin-react ^7.27.1
• eslint-plugin-react-hooks ^4.3.0
• eslint-plugin-testing-library ^5.0.1
• read-pkg-up ^7.0.1
• @types/confusing-browser-globals ^1.0.0
• eslint-find-rules ^4.0.0
• eslint ^8.4
• prettier ^2.5
• typescript ^4.5

configs/semantic-release/package.json

• @semantic-release/changelog ^6.0.1
• @semantic-release/git ^10.0.1
• conventional-changelog-conventionalcommits ^4.6.3
• read-pkg ^5.2.0
• semantic-release-vsce ^3.5.0
• @types/conventional-changelog-writer ^4.0.1
• @types/conventional-commits-parser ^3.0.2
• conventional-changelog-writer ^5.0.0
• conventional-commits-parser ^3.2.3
• semantic-release ^18.0
• semantic-release-monorepo ^7.0

configs/tsconfig/package.json

• typescript ^4.5

package.json

• @commitlint/cli ^15.0.0
• @commitlint/cz-commitlint ^15.0.0
• @types/semantic-release ^17.2.3
• commitizen ^4.2.4
• eslint ^8.4.1
• husky ^7.0.4
• inquirer ^8.2.0
• lint-staged ^12.1.4
• prettier ^2.5.1
• semantic-release ^18.0.1
• semantic-release-monorepo ^7.0.5
• typescript ^4.5.4
• yarn 3.1.1

---

• Check this box to trigger a request for Renovate to run again on this repository

----------

This issue contains a list of Renovate updates and their statuses.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): maintain lock-file

Pending Status Checks

These updates await pending status checks. To force their creation now, click the checkbox below.

• build(deps-dev): update dependency semantic-release to ^17.4.5
• build(yarn): update dependency yarn to v3.0.1
• build(deps): update dependency read-pkg to v7

Latipun Dashboard

This issue provides visibility into Renovate updates and their statuses. Learn more

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): maintain lock-file

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• ci(actions): update actions/checkout to v2.4.0
• build(deps-dev): update eslint to v8

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• build(deps): update read-pkg to v7

[releaserc] Make plugin configuration global to reduce duplication

Motivation

semantic-release support plugin configuration defined in global scope, not specific in the plugin array.

Blocked by

• pmowrer/semantic-release-monorepo#110

Make `semantic-release` plugin that support `yarn berry` publish command

Problem

semantic-release don't use yarn command when publishing so when using yarn workspace protocol, it didn't replace the protocol when published to npm.

{
  "dependencies": {
    "foo": "workspace:*",
    "bar": "workspace:^1.2.3",
    "baz": "workspace:path/to/baz"
  }
}

Try to solve semantic-release/npm#382

Possible Solution

Based on @semantic-release/npm
The gist is:

• Detect the project if it's using yarn 2. All yarn 2 project always has .yarnrc.yml file in the root project, or the yarn.lock file always contain __metadata while yarn 1 not.
• If the project using yarn 2, use yarn publishing command (yarn npm publish)