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

Update deps.yaml #1966

Merged
merged 1 commit into from
Oct 10, 2023
Merged

Update deps.yaml #1966

merged 1 commit into from
Oct 10, 2023

Conversation

JBWatenbergScality
Copy link
Contributor

What does this PR do, and why do we need it?

Which issue does this PR fix?

fixes #

Special notes for your reviewers:

@bert-e
Copy link
Contributor

bert-e commented Oct 10, 2023

Hello jbwatenbergscality,

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.

@bert-e
Copy link
Contributor

bert-e commented Oct 10, 2023

Incorrect fix version

The Fix Version/s in issue ZENKO-4666 contains:

  • None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 2.8.8

Please check the Fix Version/s of ZENKO-4666, or the target
branch of this pull request.

@bert-e
Copy link
Contributor

bert-e commented Oct 10, 2023

Waiting for approval

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

  • the author

  • 2 peers

@JBWatenbergScality
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Oct 10, 2023

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/2.8

The following branches will NOT be impacted:

  • development/2.5
  • development/2.6
  • development/2.7

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: approve

@JBWatenbergScality
Copy link
Contributor Author

/status

@bert-e
Copy link
Contributor

bert-e commented Oct 10, 2023

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

  • ✔️ development/2.8

The following branches have NOT changed:

  • development/2.5
  • development/2.6
  • development/2.7

Please check the status of the associated issue ZENKO-4666.

Goodbye jbwatenbergscality.

@bert-e bert-e merged commit b8687d5 into development/2.8 Oct 10, 2023
16 of 17 checks passed
@bert-e bert-e deleted the bugfix/ZENKO-4666 branch October 10, 2023 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants