Skip to content

Update release-it version to 19.2.4#192

Closed
mareknovotny wants to merge 1 commit intomainfrom
release-it-upgrade
Closed

Update release-it version to 19.2.4#192
mareknovotny wants to merge 1 commit intomainfrom
release-it-upgrade

Conversation

@mareknovotny
Copy link
Copy Markdown
Member

Thank you for submitting this pull request

fixes https://github.com/kiegroup/git-backporting/security/dependabot/65

Description

How Has This Been Tested?

Checklist

  • Tests added if applicable.
  • Documentation updated if applicable.

Merge criteria:

  • The commits and have meaningful messages; the author will squash them after approval or will ask to merge with squash.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

Note: dist/cli/index.js and dist/gha/index.js are automatically generated by git hooks and gh workflows.

First time here?

This project follows git conventional commits pattern, therefore the commits should have the following format:

<type>(<optional scope>): <subject>
empty separator line
<optional body>
empty separator line
<optional footer>

Where the type must be one of [build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test]

NOTE: if you are still in a work in progress branch and you want to push your changes remotely, consider adding --no-verify for both commit and push, e.g., git push origin <feat-branch> --no-verify - this could become useful to push changes where there are still tests failures. Once the pull request is ready, please amend the commit and force-push it to keep following the adopted git commit standard.

How to prepare for a new release?

There is no need to manually update package.json version and CHANGELOG.md information. This process has been automated in Prepare Release Github workflow.

Therefore whenever enough changes are merged into the main branch, one of the maintainers will trigger this workflow that will automatically update version and changelog based on the commits on the git tree.

More details can be found in package release section of the README.

@github-actions
Copy link
Copy Markdown
Contributor

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 89.37% 555/621
🟢 Branches 85.48% 259/303
🟢 Functions 87.92% 131/149
🟢 Lines 89.22% 538/603

Test suite run success

218 tests passing in 18 suites.

Report generated by 🧪jest coverage report action from 085f509

@mareknovotny mareknovotny deleted the release-it-upgrade branch March 19, 2026 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant