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.

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

chore(main): Preparing Next Release for anemoi-graphs 0.4.3 #110

Merged

Conversation

DeployDuck
Copy link
Collaborator

@DeployDuck DeployDuck commented Feb 4, 2025

🤖 Automated Release PR

This PR was created by release-please to prepare the next release. Once merged:

  1. A new version tag will be created
  2. A GitHub release will be published
  3. The changelog will be updated

Changes to be included in the next release:

0.4.3 (2025-02-04)

What's Changed

Graphs

Other Changes

Full Changelog: anemoi-graphs-0.4.2...anemoi-graphs-0.4.3


Important

⚠️ Merging this PR will:

  • Create a new release
  • Trigger deployment pipelines
  • Update package versions

Before merging:

  • Ensure all tests pass
  • Review the changelog carefully
  • Get required approvals

Release-please documentation

@github-actions github-actions bot added the graphs label Feb 4, 2025
@DeployDuck DeployDuck force-pushed the release-please--branches--main--components--anemoi-graphs branch from e549478 to 7bc109d Compare February 4, 2025 14:05
@DeployDuck DeployDuck force-pushed the release-please--branches--main--components--anemoi-graphs branch from 7bc109d to c6e38ea Compare February 4, 2025 14:08
@gmertes gmertes marked this pull request as ready for review February 4, 2025 14:11
@gmertes gmertes merged commit 4808dfc into main Feb 4, 2025
31 checks passed
@gmertes gmertes deleted the release-please--branches--main--components--anemoi-graphs branch February 4, 2025 14:13
@DeployDuck
Copy link
Collaborator Author

🤖 Created releases:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants