Skip to content

Releases: SINTEF/ci-cd

v2.5.2

04 Oct 08:05
Compare
Choose a tag to compare

Include extra toggle for releasing latest MkDocs version

It is now possible to not release a latest MkDocs documentation version. This is a feature specific to releasing documentation in the MkDocs framework and is backwards compatible, as the default value is true, i.e., keeping with the current behavior if no action is taken by users.

Furthermore, some GH Actions were updated.

Changelog

v2.5.2 (2023-10-04)

Full Changelog

Implemented enhancements:

  • Toggle latest alias MkDocs release #187

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v2.5.1

30 Aug 09:00
Compare
Choose a tag to compare

Patch release for regression fix

This release fixes a regression for the --full-docs-dir input to the docs-api-reference pre-commit hook, which happened after implementing Windows support.

Furthermore, the CD - Release callable workflow has been made less strict concerning release tag naming. Semantic versioning is still required.

Changelog

v2.5.1 (2023-08-30)

Full Changelog

Fixed bugs:

  • Regression in --full-docs-dir input #174
  • Too strict release tag name requirements #172

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v2.5.0

29 Aug 12:41
Compare
Choose a tag to compare

Support for Windows

Support and tests for Windows has been added for the pre-commit hooks.

The documentation has been updated as well with an improved distinction between single and multi-line inputs.

Changelog

v2.5.0 (2023-08-29)

Full Changelog

Fixed bugs:

  • pylint_options not working as intended #169
  • Pre-commit for documentation not working on windows #160

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v2.4.0

23 May 12:31
Compare
Choose a tag to compare

Several QoL updates and ignore rule fixes

The ignore input has been given an overhaul for more easy readability in the code, as well as ensuring it works as intended.
There is still an open issue regarding version ranges, which should be fixed (#141).

Several other QoL updates have been implemented throughout the codebase, callable workflows and more.

Changelog

v2.4.0 (2023-05-23)

Full Changelog

Implemented enhancements:

  • Automatically merge CI workflow to update deps #101
  • Support Sphinx for documentation building #90
  • Add hook for using the update-deps task #24

Fixed bugs:

  • Flawed logic #152
  • Error in workflow #150
  • Issues with the ignore-functionality of ci-cd update-deps #130

Closed issues:

  • Error in .github/workflows/ci_automerge_prs.yml which makes automerging fail in outside repos #139

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v2.3.1

13 Apr 09:19
Compare
Choose a tag to compare

Update GitHub Actions

A patch update to ensure the latest GitHub Actions are used in the callable workflows.

Changelog

v2.3.1 (2023-04-13)

Full Changelog

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v2.3.0

24 Mar 16:04
Compare
Choose a tag to compare

GitHub usernames in release changelogs

The GitHub release changelogs added by CD - Release will now use GitHub handles/usernames instead of markdown links, which will make GitHub aware of the contributors to each release.

The release_branch input for the CD - Release callable workflow is now required.

As a hot-fix, the CI - Check pyproject.toml dependencies has been fixed when calling ci-cd update-deps, where a wrongly named option argument was used.

Changelog

v2.3.0 (2023-03-24)

Full Changelog

Implemented enhancements:

  • Use GH usernames for release changelogs #102

Fixed bugs:

  • Wrongly named option used in callable workflow #125
  • Use codecov upload token #119

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v2.2.1

15 Mar 09:58
Compare
Choose a tag to compare

Hotfix for CI - Activate auto-merging for PRs

Referencing the changes input in this callable workflow was flawed in two places and has now been fixed.

Changelog

v2.2.1 (2023-03-15)

Full Changelog

Fixed bugs:

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v2.2.0

10 Mar 15:02
Compare
Choose a tag to compare

More version control for updating pyproject.toml

The new ignore option adds more version when determining whether a dependency should be updated or not when running the CI - Check pyproject.toml dependencies workflow.
To learn more about how it works, see this part of the updated documentation.

The Python API of the repository has also been documented and added to the published documentation. Unfortunately, the actual invoke functions are not rendered. This should be fixed in a later release.

Changelog

v2.2.0 (2023-03-10)

Full Changelog

Implemented enhancements:

  • Add API reference documentation for this repository #113
  • Allow to skip or keep dependency at certain level #95

Fixed bugs:

  • fail_fast should still make update-deps task fail #112

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v2.1.0

07 Feb 09:02
Compare
Choose a tag to compare

Allow changes prior to auto-merging

You can now perform custom changes prior to activating auto-merging (of dependency PRs). This is done through the perform_changes input for the CI - Activate auto-merging for PRs callable workflow.

Furthermore, a fix was implemented to always prefer the PAT secret over the GITHUB_TOKEN, if the PAT is available.

Changelog

v2.1.0 (2023-02-07)

Full Changelog

Implemented enhancements:

  • Use custom token when possible #104
  • Extend "automerge" workflow with changes #69

Closed issues:

  • Acknowledge testing dependencies in pyproject.toml #93

Merged pull requests:

* This Changelog was automatically generated by github_changelog_generator

v2.0.0

06 Dec 15:04
Compare
Choose a tag to compare

New major version - no more moving vMAJOR tag

The main reason for moving to v2, is to avoid having a dynamic vMAJOR tag (e.g., v1). For backwards compatibility, the current v1 tag will continue to exist, but there will not be a v2 tag.
This is mainly due to issues with pre-commit when updating the version it would always update to v1, which it would then not update locally further, due to the tag being dynamic.
This also means a full version must be used in the callable workflows.

Changelog

v2.0.0 (2022-12-06)

Full Changelog

Implemented enhancements:

  • Make test: true actually work for "CD - Release" #83

Fixed bugs:

  • Bad usage of backticks in warning message #79

Closed issues:

  • Drop using a vMAJOR dynamic tag #81

Merged pull requests:

  • [Auto-generated] Update dependencies #85 (TEAM4-0)
  • Changed to vMajor tag for pre-commit in ci_update_dependencies.yml #82 (francescalb)
  • Use quotes instead of backticks in warning message #80 (CasperWA)

* This Changelog was automatically generated by github_changelog_generator