gitlab-releaser - npm Package Versions

v6.0.0 (2023-09-24)

Changed

• BREAKING: Changed output from shell script to JSON file compatible with new release-cli create-from-file command. (#56)
  • The previous .gitlab/release.json files as input are no longer supported and must be converted to gitlab-releaser files. See the README for details (add release under defaults). This old schema differs from the new schema supported by release-cli, so this was removed to avoid confusion.
    • Because of this, the --schema CLI option has also been removed.
  • Environment variables in release properties are now expanded and included in the release.json file rather than being included in the shell script and expanded when the release is created. If a variable to be expanded is not set, gitlab-releaser will fail. There is a new CLI option to allow empty variables if desired (--allow-empty-variables). In this case the variables are not expanded. (#57)
  • Exported functions changed names from getReleaseCliCommand/saveReleaseCliScript to getReleaseData/saveReleaseFile.
  • See the README for changes to GitLab CI jobs.
  • Requires release-cli v0.16.0 or later.
• BREAKING: Deprecated support for Node 14 (end-of-life 2023-04-30), Node 16 (end-of-life 2023-09-11), and 19 (end-of-life 2023-06-01). Compatible with all current and LTS releases (^18.12.0 || >=20.0.0). (#50)
• BREAKING: Changed package main to exports with only the default export. Only breaking if an internal module is imported.

Fixed

• Updated examples to use the variables:expand option, added in GitLab 15.8. (#48)
• Updated to latest dependencies (ci-logger@6.0.0, commander@11.0.0, gitlab-ci-env@9.0.0, releaselog@4.0.1)
• Moved from markdownlint-cli to markdownlint-cli2.

Miscellaneous

• Updated to publish to NPM with provenance.
• Updated Renovate config for v36.

v5.0.1 (2023-03-26)

Fixed

• Updated to latest dependencies (ci-logger@5.1.1, releaselog@^3.0.4).

v5.0.0 (2023-01-30)

Changed

• BREAKING: Update changelog processing to report error and exit if the changelog description is used, but the description that was found is empty. This is almost always a changelog formatting or content issue. (#47)
• Add CLI option -c/--changelog to specify the path to the changelog, which can be a file or a directory. (#42)
• BREAKING: Refactored the getReleaseCliCommand function to accept an options object with all options. This is only breaking if that function is used programmatically and not via the CLI. (#47)

Fixed

• Updated to latest dependencies (ajv@8.12.0, commander@10.0.0, releaselog@3.0.3)

v4.0.4 (2023-01-01)

Fixed

• Updated to latest dependencies (ajv@8.11.2, gitlab-ci-env@7.0.0)

v4.0.3 (2022-10-30)

Fixed

• Updated to latest dependencies (commander@9.4.1, gitlab-ci-env@6.4.0, releaselog@3.0.2)

Miscellaneous

• Updated pipeline to have long-running jobs use GitLab shared medium sized runners. (#46)

v4.0.2 (2022-08-28)

Fixed

• Updated to latest dependencies (ci-logger to ^5.1.0, gitlab-ci-env to ^6.2.2)
• Refactored input file schema tests to reduce duplication and improve extensibility. (#45)
• Refactored tests for breaking changes in jest@29.0.1

v4.0.1 (2022-07-31)

Fixed

• Updated to latest dependencies

v4.0.0 (2022-05-30)

Changed

• BREAKING: Deprecated support for Node 12 and 17 since end-of-life. Compatible with all current and LTS releases (^14.15.0 || ^16.13.0 || >=18.0.0). (#40, #41)

Fixed

• Refactored changelog processing to reference release name instead of tag for clarity. (#44, #35)

Miscellaneous

• Added prettier and disabled eslint formatting rules. (#39)
• Added test coverage threshold requirements (#43)

v3.0.0 (2022-03-27)

Changed

• BREAKING: Update application to cover the cases where the release name in a gitlab-releaser.json or CHANGELOG are different from the git tag. (#35)
  • Changed CLI argument -t/--tag to -r/--release to reflect how this value is now used, which is only to apply release-specific data from a gitlab-releaser.json file or to retrieve values from a CHANGELOG. The default value is still $CI_COMMIT_TAG. Any scripts using the -t/--tag arguments must be updated to -r/--release.
  • The --release value no longer overrides a tag_name in the release script. If a tag_name value is specified in a release.json or gitlab-releaser.json file it will be included in the resulting release script, otherwise no tag_name will be included (in which case GitLab release-cli will use its default value of $CI_COMMIT_TAG).
  • Thanks to @reggie-k for identifying this use case.

Fixed

• Refactored to comply with latest eslint rules
• Updated to latest dependencies, including resolving CVE-2021-44906 (dev only)
• Update jsdoc comments for consistency and completeness (#10)

Miscellaneous

• Registered project for badge
• Updated project policy documents (CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md) (#37)

v2.0.4 (2022-01-23)

Fixed

• Updated to latest dependencies