Skip to content

Releases: gitlabform/gitlabform

v5.0.0-beta.3

06 Nov 13:23

Choose a tag to compare

v5.0.0-beta.3 Pre-release
Pre-release

5.0.0-beta.3

Chore

  • Rebased onto v4.6.1

v4.6.1

06 Nov 13:32

Choose a tag to compare

4.6.1

Bug Fixes

Dependencies

  • Update various dependencies to newer version.

Thanks to all the contributors of this release!

v4.6.0

01 Oct 13:34

Choose a tag to compare

4.6.0

Features

Tests

Dependencies

  • Update various dependencies to newer version.

Thanks to all the contributors of this release!

v5.0.0-beta.2

18 Sep 10:55

Choose a tag to compare

v5.0.0-beta.2 Pre-release
Pre-release

5.0.0-beta.2

Bug Fixes

  • Fix for Branch Protection changes, GitlabForm attempted to updated users when config has not changed from Gitlab, resulting in API errors and a failed run of GitlabForm. #1107 (TimKnight-DWP)

Variables with same name but different scope should be deletable #962 (amimas)

As per the referenced issue #533, if there are multiple CI CD variables with same key/name but scoped to different "environment", gitlabform does not make the API call correctly. As a result, the variable cannot be deleted and an error is returned.

Bug fix includes a large refactor to use python-gitlab code and tidy up redundant paths, hence being included as part of v5 Release Candidate testing.

v5.0.0-beta.1

08 Sep 11:32

Choose a tag to compare

v5.0.0-beta.1 Pre-release
Pre-release

5.0.0-beta.1

Breaking Changes

Branch Protection Updates #1070 (TimKnight-DWP & br0ziliy)

When preventing GitlabForm from un-protecting and then re-protecting the Branch in order to apply configuration changes to the protection rules #1070, we discovered some functionality that was previously hidden from the user.

Previously if you stopped defining code_owner_approval_required or allow_force_push in the YAML config, the settings would revert to the default Gitlab settings applied when first protecting the branch, see: Branch Protection API

With the changes to perform dynamic updates as required, we follow the GitlabForm convention of leaving the Gitlab settings as is if the data is no longer defined in configuration.

Therefore, if you wish to ensure the Protected Branch settings are applied as you intend when running GitlabForm you should define some defaults explicitly:

projects_and_groups:
 my-group/*:
   branches:
     main:
       protected: true
       allow_force_push: false
       code_owner_approval_required: true

Full details: docs/reference/protected_branches.md

  • Extension of: #996

Resolves:

v4.5.0

08 Sep 11:01

Choose a tag to compare

4.5.0

Features

Documentation

  • Update ci_cd_variables.md to include raw variable example #1091. (uob-hillmu)

Dependencies

  • Update various dependencies to newer version.

Thanks to all the contributors of this release!

v4.4.1

11 Aug 12:58

Choose a tag to compare

4.4.1

Bug Fixes

  • Group SAML Link config changes should be applied. Resolves #994, PR #1076. (amimas)

Tests

  • Improve branch protection tests #1066. (TimKnight-DWP)
  • Add smoke tests for python 3.13
  • Add acceptance test for group ldap links #1079. (amimas)

Dependencies

  • Update various dependencies to newer version.
  • Update Dockerfile to use latest version of Alpine

Thanks to all the contributors of this release!

v4.4.0

30 Jul 10:42

Choose a tag to compare

4.4.0

Features

Documentation

Dependencies

  • Update various dependencies to newer version.

Thanks to all the contributors of this release!

v4.3.0

23 Jul 11:27

Choose a tag to compare

4.3.0

Chores

Features

Dependencies

  • Update various dependencies to newer version.

Thanks to all the contributors of this release!

v4.2.6

07 Jul 15:24

Choose a tag to compare

4.2.6

Bug Fixes

Tests

Dependencies

  • Update various dependencies to newer version.

Thanks to all the contributors of this release!