sounisi5011 / package-version-git-tag Goto Github PK

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.

• ⬆️ Update dependency @types/cross-spawn to v6.0.6
• ⬆️ Update dependency @types/mock-fs to v4.13.4
• ⬆️ Update dependency @types/which-pm-runs to v1.0.2
• ⬆️ Update dependencies: npm-scripts packages (del-cli, npm-run-all)
• ⬆️ Update dependency @go-task/cli to v3.37.2
• ⬆️ Update actions/cache action to v4
• ⬆️ Update actions/checkout action to v4
• ⬆️ Update actions/github-script action to v7
• ⬆️ Update actions/setup-node action to v4
• ⬆️ Update dependencies: test packages (major) (execa, vitest)
• ⬆️ Update dependency @tsconfig/node14 to v14
• ⬆️ Update dependency prettier to v3
• 🔐 Create all rate-limited PRs at once 🔐

Open

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

• ⬆️ Update dependency vite to v4.5.3 [SECURITY]
• ⬆️ Update dependencies: test packages (@sindresorhus/slugify, @types/semver, execa, semver, ts-node, vitest)
• ⬆️ Update dependency @types/node to v14.18.63
• ⬆️ Update dependencies: code formatter packages (lefthook, prettier, sort-package-json)
• ⬆️ Update dependencies: eslint packages (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint, eslint-config-prettier, eslint-config-standard, eslint-plugin-import, eslint-plugin-n, eslint-plugin-promise, eslint-plugin-vitest)
• ⬆️ Update pnpm to v7.33.7
• ⬆️ Update FantasticFiasco/action-update-license-year action to v3
• ⬆️ Update dependencies: eslint packages (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint, eslint-config-prettier, eslint-plugin-n, eslint-plugin-prettier, eslint-plugin-simple-import-sort)
• ⬆️ Update dependency typescript to v5
• ⬆️ Lock file maintenance
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

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

• Drop support for Node.js 10 and 12 - resolved #186

• Support Node.js 16 and 18 - resolved #171 and #197

• Migrate from AVA to Vitest - resolved #200

• Update or migrate cac package - resolved #211

• Move from CommonJS to ESM - resolved #227
  Some dependencies moved to pure ESM.
  However, this CLI is not yet a pure ESM and cannot update these dependencies.

  The primary use of this CLI is in the release process, so there is no need to support the old Node.js.
  Therefore, it should be possible migrate to a pure ESM.

• Remove release scripts and use GitHub Actions for automatic releases
  Package is-git-status-clean in the dependencies depends on package trim-newlines@^2.0.0 with known vulnerabilities.
  However, this package is only used for manual releases.
  If releases are automated, this dependency is not needed.
  The release process should be automated, not only to remove vulnerable dependencies, but also to prevent human error.

• Use the prefix [command] when executing on GitHub Actions
  This prefix allows highlighting of the command executed within the output of GitHub Actions.
  see https://github.com/actions/toolkit/blob/a91ee0b497d90e7352290ea416f4403e7792aacf/packages/exec/src/toolrunner.ts#L47

Assuming standard GitHub, the format of the version tag is v{version}.
However, some people may want to change this format.
Perhaps it is an edge case, but better than the current situation where there is no choice.

This CLI tool has no help document to browse on the console.
If we follow the standard other commands and use the --help option, the documentation will not be displayed, and Git tags will be added silently.

This command is very simple, but I may still want to know what happens.
It is useful to have the --dry-run option.

I'm using Node.js 15.8.0 and the installation fails with:

error [email protected]: The engine "node" is incompatible with this module. Expected version "10.x || 12.x || 14.x". Got "15.8.0"
error Found incompatible module.

I can hardly imagine that a new Node.js version could break the functionality of this package. Is it really necessary to limit the maximum Node.js version?

There may be multiple remote repositories configured in Git.
The name of the remote repository is often "origin", but this is not the default built in Git.

If remote repositories other than "origin" are set, the option to select them is required.

There are two types of Git tags: lightweight and annotated.
The lightweight tag is only an alias for commit. Annotated tags, on the other hand, contain information such as the tagger name and date.
Because of this feature, documents on Web state that annotated tags are recommended over lightweight tags.

A lightweight tag is very much like a branch that doesn’t change — it’s just a pointer to a specific commit.

Annotated tags, however, are stored as full objects in the Git database. They’re checksummed; contain the tagger name, email, and date; have a tagging message; and can be signed and verified with GNU Privacy Guard (GPG). It’s generally recommended that you create annotated tags so you can have all this information

─ https://git-scm.com/book/en/v2/Git-Basics-Tagging#_creating_tags

It is useful to have the feature to detect duplicate tags and replace them with annotated tags if they are lightweight.

Here is the answer to help you detect the type of tag:

• https://stackoverflow.com/a/40499437/4907315 - Use git for-each-ref refs/tags