Skip to content

Releases: gitlabform/gitlabform

v1.0.4

19 Dec 13:11
452934a
Compare
Choose a tag to compare

Added Pipelines API support (not used by cli gitlabform yet).

v1.0.1

28 Sep 10:59
Compare
Choose a tag to compare

Fixes #30

This release fixes problems with finding branches .

v1.0.0

04 Aug 18:46
Compare
Choose a tag to compare

This version switches from using GitLab API v3 to v4 to make it compatible with GitLab 11+.

Note that this change will most probably require an update of your config.yml as GitLabForm takes some parameter names from this file directly and they have changed in API v4. See changes in config.yml in this diff for a few examples: https://github.com/egnyte/gitlabform/pull/28/files

This version should also be a lot faster as we reduced the number of API calls by about 50% (!) by using "group/project" as a parameter wherever possible instead of querying for project id before each call that actually does something first. (Yes, I know that we could have cached that project id from the start :P but this was not trivial under current app design.)

v0.23.0

29 Apr 13:59
Compare
Choose a tag to compare

With support for configuring project-level Merge Requests approval settings and approvers list (#26).

v0.22.0

06 Jan 19:28
Compare
Choose a tag to compare

With support for simple templating - only {{ group }} and {{ project }} are supported
for now, no escaping. Fixes #15 .

v0.21.0

18 Nov 19:15
Compare
Choose a tag to compare

With #9, #17 and #18 fixed. No new features really, so perhaps this should rather be still v0.20.x but it's too late now. ;)

v0.20.0

16 Nov 15:11
Compare
Choose a tag to compare

Allow setting file contents from external files, not only embedded in the config.yml (#5). See updated config.yaml for examples.

v0.19.1

04 Oct 14:38
Compare
Choose a tag to compare

With fixed a bug that made run with ALL fail on first project that has no config.

v0.19.0

03 Oct 16:39
Compare
Choose a tag to compare

Now we have 3 configuration levels: common (new!), group and project. And you can run gitlabform with all projects your access token allows. This way it's possible to configure things for all projects in your GitLab instance. See updated config.yaml for examples.

Note: the cli api has changed - ALL now means all projects you have access to, while ALL_DEFINED means, well, all projects and groups defined in the config. This is safe though because if you only upgrade gitlabform without updating the config you will not have the new common_config: key and no new projects will be configured.

v0.18.0

20 Sep 09:06
Compare
Choose a tag to compare

With added possibility to make selected file changes not trigger CI builds
(disabled by default, set skip_ci to true to enable it, see example config.yml)
and some minor fixes.