Skip to content

chore(master): release 4.0.0 #578

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
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(master): release 4.0.0 #578

wants to merge 1 commit into from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 10, 2024 •
edited
Loading

🤖 I have created a release beep boop

4.0.0 (2025-03-16)

⚠ BREAKING CHANGES

  • support asdf >= v0.16.0 (#590)

Features

Patches

  • remove origin argument from git checkout command (#591) (179e953)

Documentation

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot requested a review from jthegedus as a code owner January 10, 2024 13:31
@github-actions github-actions bot force-pushed the release-please--branches--master--components--actions branch from 0dae264 to 593e38f Compare January 10, 2024 13:31
@github-actions github-actions bot force-pushed the release-please--branches--master--components--actions branch from 593e38f to 8d5eeec Compare January 22, 2025 20:17
@github-actions github-actions bot changed the title chore(master): release 3.0.3 chore(master): release 4.0.0 Mar 14, 2025
@github-actions github-actions bot force-pushed the release-please--branches--master--components--actions branch 2 times, most recently from 91b61f0 to d794daa Compare March 16, 2025 14:53
@github-actions github-actions bot force-pushed the release-please--branches--master--components--actions branch from d794daa to 8bf4856 Compare March 16, 2025 15:00
@dannysauer dannysauer mentioned this pull request Mar 25, 2025
Open
@DeadManPoe
Copy link

@jthegedus May I ask if you have in mind some date to merge this PR and effectively release the v4 action? Thanks

@landonpoch
Copy link

Is this blocked by something? Maybe there is there still testing that is occurring for the v4 release? I've been seeing notices in my build pipelines that are using v3 for a while now so I figured I'd look into upgrading. Looks like everything is ready but we're just missing a tag.

@dannysauer
Copy link

This is implied to be done by PR #590, but issue #594 suggests that not to be the case.

Someone call housekeeping; there's a spill in Aisle v4. ;)

@maxromanovsky
Copy link

Please, please release a new version :)

@Stratus3D
Copy link
Member

@jthegedus @smorimoto can we ship this now?

@Stratus3D Stratus3D mentioned this pull request May 2, 2025
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Stratus3D Stratus3D Stratus3D approved these changes

@jthegedus jthegedus Awaiting requested review from jthegedus jthegedus is a code owner

Assignees
No one assigned
Labels
autorelease: pending
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@DeadManPoe @landonpoch @dannysauer @maxromanovsky @Stratus3D