-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
release update #10296
release update #10296
Conversation
…ean-codeclimate-after-`drops-refactor`-merge
🔧 cookie banner btn design
graceful handle of url check
fix: New warpcast mint landing notif
fix: When transaction failed, opening modal resets the state weirdly
…de-checker/expend-webgl-check
…of-packages [skip netlify] Update Bumped minor version of packages
Expand web gl check to all js files
fix: Clicking followed by should open followers tab
beta update
✅ Deploy Preview for koda-canary ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for koda-beta ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Quality Gate passedIssues Measures |
cc @prury are there any bug fixes which should be merged into prod ? |
making a fast comparison, i think this release is pretty much the sum of what we merged to beta + recent merged stuff in my mind it worked differently, like the following: batch 1 of PRs goes to beta and then release PR would merge this same batch into prod what do i think its happening: batch 1 of PRs goes to beta and then release PR would merge batch1 + newbatch into prod can you check it? |
Yes, they are the same, Q is if there is anything in beta that needs to be fixed, or is it safe to release this one |
i believe it is safe, i will check prod right after, ty |
Release Update