Skip to content

Auto-rebase: next onto latest develop #1488

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

Open
wants to merge 31 commits into
base: next
Choose a base branch
from

Conversation

polymesh-bot
Copy link

This PR is automatically created by the auto-rebase workflow. It rebased the next branch onto latest develop and raised the PR including all merge conflicts.
Please review and merge it.

NOTE: Merge conflicts are not resolved in this PR and the commits from next needs to be resigned.

Once all the merge conflicts are resolved and commits from next branch have been signed, you can use the following commands to merge this PR:

git branch -f next rebase-next-1747312723
git push -f origin next

The above command will forcefully move the next branch to top of this PR head and merge the PR.

F-OBrien and others added 30 commits April 4, 2025 12:25
BREAKING CHANGE: 🧨 Return of trustedClaimIssuers.get() will be an object for custom claim
containing customClaimTypeId
@polymesh-bot polymesh-bot requested a review from a team as a code owner May 15, 2025 12:38
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.

5 participants