Skip to content

Backport of bump ui commit to 5d6e65f into release/0.19.x#5873

Closed
hc-github-team-secure-boundary wants to merge 1 commit intorelease/0.19.xfrom
backport/bump-ui-commit-5d6e65f/likely-resolved-polliwog
Closed

Backport of bump ui commit to 5d6e65f into release/0.19.x#5873
hc-github-team-secure-boundary wants to merge 1 commit intorelease/0.19.xfrom
backport/bump-ui-commit-5d6e65f/likely-resolved-polliwog

Conversation

@hc-github-team-secure-boundary
Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #5871 to be assessed for backporting due to the inclusion of the label backport/0.19.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@priya-patel04
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/boundary/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


Original PR had no description content.


Overview of commits

@moduli
Copy link
Copy Markdown
Collaborator

moduli commented Feb 12, 2026

Handled by #5896

@moduli moduli closed this Feb 12, 2026
@moduli moduli deleted the backport/bump-ui-commit-5d6e65f/likely-resolved-polliwog branch February 12, 2026 15:09
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.

3 participants