-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
upgrade macos version #10974
upgrade macos version #10974
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10974 +/- ##
==========================================
- Coverage 89.14% 89.08% -0.06%
==========================================
Files 183 183
Lines 23553 23553
==========================================
- Hits 20996 20983 -13
- Misses 2557 2570 +13
Flags with carried forward coverage won't be shown. Click here to find out more.
|
6536e9f
to
54f5378
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.8.latest 1.8.latest
# Navigate to the new working tree
cd .worktrees/backport-1.8.latest
# Create a new branch
git switch --create backport-10974-to-1.8.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0c51985c8388dab210a8fb659b08b7cb14bc3427
# Push it to GitHub
git push --set-upstream origin backport-10974-to-1.8.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.8.latest Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.7.latest 1.7.latest
# Navigate to the new working tree
cd .worktrees/backport-1.7.latest
# Create a new branch
git switch --create backport-10974-to-1.7.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0c51985c8388dab210a8fb659b08b7cb14bc3427
# Push it to GitHub
git push --set-upstream origin backport-10974-to-1.7.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.7.latest Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.5.latest 1.5.latest
# Navigate to the new working tree
cd .worktrees/backport-1.5.latest
# Create a new branch
git switch --create backport-10974-to-1.5.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0c51985c8388dab210a8fb659b08b7cb14bc3427
# Push it to GitHub
git push --set-upstream origin backport-10974-to-1.5.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.5.latest Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.6.latest 1.6.latest
# Navigate to the new working tree
cd .worktrees/backport-1.6.latest
# Create a new branch
git switch --create backport-10974-to-1.6.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0c51985c8388dab210a8fb659b08b7cb14bc3427
# Push it to GitHub
git push --set-upstream origin backport-10974-to-1.6.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.6.latest Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.4.latest 1.4.latest
# Navigate to the new working tree
cd .worktrees/backport-1.4.latest
# Create a new branch
git switch --create backport-10974-to-1.4.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 0c51985c8388dab210a8fb659b08b7cb14bc3427
# Push it to GitHub
git push --set-upstream origin backport-10974-to-1.4.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.4.latest Then, create a pull request where the |
* upgrade to macos-latest * force link # Conflicts: # .github/actions/setup-postgres-macos/action.yml
* upgrade to macos-latest * force link # Conflicts: # .github/actions/setup-postgres-macos/action.yml
* upgrade to macos-latest * force link # Conflicts: # .github/actions/setup-postgres-macos/action.yml
* upgrade to macos-latest * force link # Conflicts: # .github/actions/setup-postgres-macos/action.yml
* upgrade to macos-latest * force link # Conflicts: # .github/actions/setup-postgres-macos/action.yml # .github/workflows/main.yml
* upgrade to macos-latest * force link # Conflicts: # .github/actions/setup-postgres-macos/action.yml # .github/workflows/main.yml
Problem
We're using macos-12 in CI and it's currently in a brownout to be fully deprecated beginning of December.
Solution
Upgrade CI.
Checklist