Skip to content

chore: update backend to v2.0.0-alpha.10#1157

Open
github-actions[bot] wants to merge 1 commit intomasterfrom
backend-update/v2.0.0-alpha.10
Open

chore: update backend to v2.0.0-alpha.10#1157
github-actions[bot] wants to merge 1 commit intomasterfrom
backend-update/v2.0.0-alpha.10

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

This PR was automatically generated by the GitHub Action .github/workflows/update-backend.yml

It updates the backend version to v2.0.0-alpha.10. For a full description of the changes, see the backend changelog: v2.0.0-alpha.10.

@MilesCranmer
Copy link
Copy Markdown
Owner

@MilesCranmerBot can you figure out why the CI isn't running? And then fix it please

@MilesCranmerBot
Copy link
Copy Markdown
Contributor

CI didn't start because this PR was opened by the github-actions bot (via create-pull-request using GITHUB_TOKEN), and GitHub suppresses workflows triggered by events created with GITHUB_TOKEN to prevent recursion.

Quick fix: push an empty commit to backend-update/v2.0.0-alpha.10 (or edit+commit any file on that branch) to trigger the normal pull_request synchronize event.

Longer-term fix: PR #1158 adds workflow_dispatch + has the backend-update workflow dispatch CI automatically.

@MilesCranmer
Copy link
Copy Markdown
Owner

@MilesCranmerBot I think we need to update this script to also handle updates to the release please manifest? Also the title of the PR's made by this script should be in conventional commits structure. Also please make it so that the CI will automatically run, because it didn't seem to last time.

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 30, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.25%. Comparing base (c435527) to head (7504e0d).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1157   +/-   ##
=======================================
  Coverage   94.25%   94.25%           
=======================================
  Files          21       21           
  Lines        1687     1687           
=======================================
  Hits         1590     1590           
  Misses         97       97           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@MilesCranmerBot
Copy link
Copy Markdown
Contributor

Done.

I couldn't push directly to backend-update/v2.0.0-alpha.10 because that branch is on MilesCranmer/PySR and this bot account doesn't have write access to that branch (maintainerCanModify is false / push got 403). So I opened a follow-up PR instead: #1166

#1166

That PR updates the backend bump automation to:

  • update .release-please-manifest.json too
  • use conventional-commit PR titles / commit messages
  • auto-dispatch the usual CI workflows for backend-update PRs, so they run even when the PR is created by automation

Commit on the bot branch: 0e8a094.

@github-actions github-actions bot force-pushed the backend-update/v2.0.0-alpha.10 branch from de27a9e to ae786d8 Compare March 31, 2026 00:27
@github-actions github-actions bot changed the title Automated update to backend: v2.0.0-alpha.10 chore: update backend to v2.0.0-alpha.10 Mar 31, 2026
@github-actions github-actions bot force-pushed the backend-update/v2.0.0-alpha.10 branch from ae786d8 to 7504e0d Compare April 2, 2026 00:25
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.

2 participants