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.

Sign up for GitHub

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

Jump to bottom

[5.1.300] corsproxy fix #3463

Merged
merged 3 commits into from
Mar 20, 2024
Merged

[5.1.300] corsproxy fix #3463

merged 3 commits into from
Mar 20, 2024

Conversation

vsubhuman
Copy link
Contributor

No description provided.

@neuodev
Copy link
Contributor

neuodev commented Mar 20, 2024 •
edited
Loading

[autoscript] ⚠️ fix/corsproxy doesn't full our branch naming convention.
Should follow <tag>/<jira-ticket-id>/<short-name>

Details
  • <tag>: fix, feat, chore, refactor, test, ...
  • <jira-ticket-id>: The issue ID of JIRA all capital letters
  • <short-name>: A short and descriptive name for the branch

@vsubhuman vsubhuman marked this pull request as ready for review March 20, 2024 12:41
@vsubhuman vsubhuman self-assigned this Mar 20, 2024
@vsubhuman vsubhuman requested a review from Nebyt March 20, 2024 12:41
@vsubhuman vsubhuman added this to the 5.1.300 milestone Mar 20, 2024
@vsubhuman vsubhuman changed the title corsproxy fix [5.1.300] corsproxy fix Mar 20, 2024
Nebyt
Nebyt previously approved these changes Mar 20, 2024
View reviewed changes
@vsubhuman
Copy link
Contributor Author

Release: https://github.com/Emurgo/yoroi-frontend/releases/tag/5.1.300

@Nebyt Nebyt self-requested a review March 20, 2024 14:23
@vsubhuman vsubhuman merged commit 28d01eb into production Mar 20, 2024
5 of 12 checks passed
@vsubhuman vsubhuman deleted the fix/corsproxy branch March 20, 2024 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Nebyt Nebyt Nebyt approved these changes

Assignees

@vsubhuman vsubhuman

Labels
hotfix release
Projects
None yet
Milestone
5.1.300
Development

Successfully merging this pull request may close these issues.
3 participants
@vsubhuman @neuodev @Nebyt