A Declarative Dependency Management tool
@dependabot, @dependabot[bot], @mcwarman, @olblak, @updateclibot and @updateclibot[bot]
@MattiasAng, @dependabot, @dependabot[bot], @olblak, @updateclibot and @updateclibot[bot]
Identified regression that will need a follow up fix
@MattiasAng, @dependabot, @dependabot[bot], @olblak, @updateclibot and @updateclibot[bot]
@MattiasAng, @dependabot, @dependabot[bot], @olblak, @updateclibot and @updateclibot[bot]
@MattiasAng, @dependabot, @dependabot[bot], @olblak, @updateclibot and @updateclibot[bot]
@MattiasAng, @dependabot, @dependabot[bot], @olblak, @updateclibot and @updateclibot[bot]
@dependabot, @dependabot[bot], @olblak, @updateclibot and @updateclibot[bot]
This release introduces a major improvement when interacting with Git repositories.
By default, Updatecli now automatically recreate "working" branch if their base branch diverges.
It relies on the scm option force
to enable/disable this behavior.
So, If a target relies on a scm configuration with the setting "force" set to "true" like in the following example:
pipelineid: example
scms:
default:
kind: github
spec:
branch: 'main'
email: '[email protected]'
owner: 'updatecli-test'
repository: 'updatecli'
token: '{{ requiredEnv "GITHUB_TOKEN" }}'
user: 'updateclibot'
username: 'alice'
# force allows recreating the working branch
# and to force push the changes by running
# git push --force
force: true
disabled: false
Then Updatecli creates a working branch named "updatecli_main_example" based on the branch "main" and each time the branch "main" is modified, Updatecli recreates the working branch "updatecli_main_example". The setting "force" allows Updatecli to recreate the working branch and to run "git push --force" operation.
As a reminder, it's always a good practice to have branch protection in place to protect sensitive branches.
The scm git plugin has force
set to false
by default because it doesn't use working branch by default.
The scm plugin github,gitlab,stash, and gitea use force
set to true by default as they all use working branch by default.
@dependabot, @dependabot[bot], @olblak, @updateclibot and @updateclibot[bot]
This release introduces a major improvement when interacting with Git repositories.
Updatecli now automatically recreate "working" branch if their base branch diverges.
It relies on the scm option force
to enable/disable this behavior.
So, If a target relies on a scm configuration with the setting "force" set to "true" like in the following example:
pipelineid: example
scms:
default:
kind: github
spec:
branch: 'main'
email: '[email protected]'
owner: 'updatecli-test'
repository: 'updatecli'
token: '{{ requiredEnv "GITHUB_TOKEN" }}'
user: 'updateclibot'
username: 'alice'
# force allows recreating the working branch
# and to force push the changes by running
# git push --force
force: true
disabled: false
Then Updatecli creates a working branch named "updatecli_main_example" based on the branch "main" and each time the branch "main" is modified, Updatecli recreates the working branch "updatecli_main_example". The setting "force" allows Updatecli to recreate the working branch and to run "git push --force" operation.
As a reminder, it's always a good practice to have branch protection in place to protect sensitive branches.
The scm git plugin has force
set to false
by default because it doesn't use working branch by default.
The scm plugin github,gitlab,stash, and gitea use force
set to true by default as they all use working branch by default.
@dependabot, @dependabot[bot], @olblak, @updateclibot and @updateclibot[bot]
This release introduces a major improvement when interacting with Git repositories. If a target relies on a scm configuration with the setting "force" set to "true" like in the following example:
pipelineid: example
scms:
default:
kind: github
spec:
branch: 'main'
email: '[email protected]'
owner: 'updatecli-test'
repository: 'updatecli'
token: '{{ requiredEnv "GITHUB_TOKEN" }}'
user: 'updateclibot'
username: 'alice'
# force allows recreating the working branch
# and to force push the changes by running
# git push --force
force: true
disabled: false
Then Updatecli creates a working branch named "updatecli_main_example" based on the branch "main" and each time the branch "main" is modified, Updatecli recreates the working branch "updatecli_main_example". The setting "force" allows Updatecli to recreate the working branch and to run "git push --force" operation.
As a reminder, it's always a good practice to have branch protection in place to protect sensitive branches.
@dependabot, @dependabot[bot], @olblak, @updateclibot and @updateclibot[bot]