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.

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

chore(main): release push-to-gar-docker 1.0.0 #419

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(main): release push-to-gar-docker 1.0.0 #419

wants to merge 1 commit into from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 27, 2024 •
edited
Loading

🤖 I have created a release beep boop

1.0.0 (2024-11-21)

🎉 Features

  • build-push-to-gar: Expose platforms parameter (#78) (f86c2ca)
  • push-to-gar-docker - add outputs for ease-of-use (#89) (6e9b07a)
  • push-to-gar-docker: replace underscores with hyphens in repo names (#199) (a67842b)

🐛 Bug Fixes

  • add repository_name input to push-to-gar-docker (#198) (264a3f2)
  • Make file argument optional in docker build actions (#50) (b2c2806)
  • push-gar-doc: fix typo (#200) (5d89d95)

📝 Documentation

  • push-to-gar-docker: Fix metadata link (#159) (1a9e4bc)

🔧 Miscellaneous Chores

  • Bump upstream docker actions (#51) (f33ebd9)
  • deps: update actions/checkout action to v4.1.7 (#244) (1d5fba5)
  • deps: update actions/checkout action to v4.2.0 (#313) (ba6268c)
  • deps: update actions/checkout action to v4.2.1 (#445) (c72e039)
  • deps: update actions/checkout action to v4.2.2 (#498) (7c6dbe2)
  • deps: update docker/build-push-action action to v5.4.0 (#253) (30f2a90)
  • deps: update docker/build-push-action action to v6 (#265) (7a88455)
  • deps: update docker/build-push-action action to v6.8.0 (#413) (1994696)
  • deps: update docker/build-push-action action to v6.9.0 (#431) (51c9559)
  • deps: update docker/metadata-action action to v5.6.0 (#539) (1bdb3a4)
  • deps: update docker/metadata-action action to v5.6.1 (1bdb3a4)
  • deps: update docker/setup-buildx-action action to v3.6.1 (#257) (46bb727)
  • deps: update docker/setup-buildx-action action to v3.7.0 (#438) (c546bd5)
  • deps: update docker/setup-buildx-action action to v3.7.1 (#440) (680fa60)

This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--push-to-gar-docker branch 7 times, most recently from 5a24134 to b6483f5 Compare October 7, 2024 07:01
@github-actions github-actions bot force-pushed the release-please--branches--main--components--push-to-gar-docker branch 7 times, most recently from c480828 to ccb5d56 Compare October 15, 2024 05:58
@github-actions github-actions bot force-pushed the release-please--branches--main--components--push-to-gar-docker branch 6 times, most recently from 02f7413 to eb668bf Compare October 23, 2024 06:27
@github-actions github-actions bot force-pushed the release-please--branches--main--components--push-to-gar-docker branch 2 times, most recently from 0f0680f to 0990ad7 Compare October 25, 2024 05:39
@eloymg eloymg force-pushed the release-please--branches--main--components--push-to-gar-docker branch from 0990ad7 to 556b928 Compare October 25, 2024 10:20
@eloymg eloymg marked this pull request as ready for review October 25, 2024 10:20
@eloymg eloymg requested a review from a team as a code owner October 25, 2024 10:20
@github-actions github-actions bot force-pushed the release-please--branches--main--components--push-to-gar-docker branch 2 times, most recently from 340abaa to 0761cc6 Compare October 30, 2024 09:42
@iainlane
Copy link
Member

I'm personally not convinced we should release this action as a v1 right now.

IMO we should make sure we at least have a common interface between the GAR and Docker Hub actions, possibly multiarch (#135) and maybe even combine the actions.

Basically I don't think the interfaces we have are something we should call a v1.

Would be interested in opinions from the rest of the team, though.

@dsotirakis
Copy link
Contributor

dsotirakis commented Oct 30, 2024 •
edited
Loading

I agree with @iainlane. I think v1 should be complete. I could be okay with releasing a v0.something.something though.
As for the multiarch builds - will prioritise to work on this the following weeks to get it merged asap.
Also issue to merge dockerhub and gar workflows #81

@github-actions github-actions bot force-pushed the release-please--branches--main--components--push-to-gar-docker branch 3 times, most recently from e14ac3a to f7be419 Compare November 8, 2024 16:41
@github-actions github-actions bot force-pushed the release-please--branches--main--components--push-to-gar-docker branch 5 times, most recently from f9bb54b to 9b57a89 Compare November 15, 2024 07:37
@github-actions github-actions bot force-pushed the release-please--branches--main--components--push-to-gar-docker branch 3 times, most recently from 88b9b5e to 11bb608 Compare November 20, 2024 07:17
@github-actions github-actions bot force-pushed the release-please--branches--main--components--push-to-gar-docker branch from 11bb608 to 6a720ea Compare November 21, 2024 06:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@eloymg eloymg eloymg approved these changes

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

Successfully merging this pull request may close these issues.
3 participants
@iainlane @dsotirakis @eloymg