Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump scality/action-artifacts from 3 to 4 #4213

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 15, 2023

Bumps scality/action-artifacts from 3 to 4.

Release notes

Sourced from scality/action-artifacts's releases.

v4

What's Changed

Full Changelog: scality/action-artifacts@3.2.6...v4

4.0.0

What's Changed

Full Changelog: scality/action-artifacts@3.2.6...4.0.0

4.0.0-beta.0

What's Changed

Full Changelog: scality/action-artifacts@3.2.6...4.0.0-beta.0

3.2.6

What's Changed

Full Changelog: scality/action-artifacts@3.2.5...3.2.6

3.2.5

What's Changed

New Contributors

... (truncated)

Commits
  • 7f62ab2 github-actions(deps): bump actions/upload-artifact from 3 to 4 (#389)
  • ff749e0 Upgrade node and dependencies (#391)
  • f28b081 Change dev setup/environment to support codespaces (#390)
  • b4e43e4 Reference branches on push event for index workflow
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot requested a review from a team as a code owner December 15, 2023 22:12
@dependabot dependabot bot added github_actions Pull requests that update GitHub Actions code kind:dependencies Pull requests that update a dependency file labels Dec 15, 2023
@bert-e
Copy link
Contributor

bert-e commented Dec 15, 2023

Hello dependabot[bot],

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

The following options are set: bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Contributor

bert-e commented Dec 15, 2023

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following options are set: bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Contributor

bert-e commented Dec 18, 2023

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following options are set: bypass_author_approval, bypass_jira_check

Bumps [scality/action-artifacts](https://github.com/scality/action-artifacts) from 3 to 4.
- [Release notes](https://github.com/scality/action-artifacts/releases)
- [Commits](scality/action-artifacts@v3...v4)

---
updated-dependencies:
- dependency-name: scality/action-artifacts
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@TeddyAndrieux TeddyAndrieux force-pushed the dependabot/github_actions/scality/action-artifacts-4 branch from 7ace103 to d59ffbb Compare January 11, 2024 09:12
@bert-e
Copy link
Contributor

bert-e commented Jan 11, 2024

Branches have diverged

This pull request's source branch dependabot/github_actions/scality/action-artifacts-4 has diverged from
development/127.0 by more than 50 commits.

To avoid any integration risks, please re-synchronize them using one of the
following solutions:

  • Merge origin/development/127.0 into dependabot/github_actions/scality/action-artifacts-4
  • Rebase dependabot/github_actions/scality/action-artifacts-4 onto origin/development/127.0

Note: If you choose to rebase, you may have to ask me to rebuild
integration branches using the reset command.

The following options are set: bypass_author_approval, bypass_jira_check

@TeddyAndrieux TeddyAndrieux changed the base branch from development/127.0 to development/126.0 January 11, 2024 09:12
@bert-e
Copy link
Contributor

bert-e commented Jan 11, 2024

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

The following options are set: bypass_author_approval, bypass_jira_check

@TeddyAndrieux
Copy link
Collaborator

/create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Jan 11, 2024

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/123.0
  • development/124.0
  • development/124.1
  • development/125.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: create_integration_branches, bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Contributor

bert-e commented Jan 11, 2024

Build failed

The build for commit did not succeed in branch w/127.0/dependabot/github_actions/scality/action-artifacts-4.

The following options are set: create_integration_branches, bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Contributor

bert-e commented Jan 11, 2024

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/126.0

  • ✔️ development/127.0

The following branches will NOT be impacted:

  • development/123.0
  • development/124.0
  • development/124.1
  • development/125.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: create_integration_branches, bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Contributor

bert-e commented Jan 11, 2024

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/126.0

  • ✔️ development/127.0

The following branches have NOT changed:

  • development/123.0
  • development/124.0
  • development/124.1
  • development/125.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

Please check the status of the associated issue None.

Goodbye dependabot[bot].

@bert-e bert-e merged commit d59ffbb into development/126.0 Jan 11, 2024
67 of 68 checks passed
@bert-e bert-e deleted the dependabot/github_actions/scality/action-artifacts-4 branch January 11, 2024 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
github_actions Pull requests that update GitHub Actions code kind:dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants