Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 23, 2025

🤖 I have created a release beep boop

cli: 1.1.0

1.1.0 (2025-01-23)

Features

  • bump to 1.1 please (4ed8ed3)
  • maybe we can just modify the release-please-manifest (e374d14)

Bug Fixes

  • bumping gitops_server (b6a1d19)
  • fix broken gitops server release process by merging with regular gitops cli release (739ead0)
  • trigger build (7afa38f)
  • trigger gitops build (0345a3b)

Miscellaneous Chores

  • trigger release for [gitops_server] (8ec041a)
  • trigger release for [gitops_server] (1389531)
helm: 1.1.0

1.1.0 (2025-01-23)

Miscellaneous Chores


This PR was generated with Release Please. See documentation.

@uptickmetachu
Copy link
Collaborator

Wow you're actually broken.

@github-actions github-actions bot force-pushed the release-please--branches--develop branch 3 times, most recently from c60b886 to b4abd82 Compare January 23, 2025 01:58
@uptickmetachu uptickmetachu force-pushed the release-please--branches--develop branch from b4abd82 to bdc9826 Compare January 23, 2025 02:07
@uptickmetachu uptickmetachu merged commit f4a152a into develop Jan 23, 2025
2 checks passed
@uptickmetachu uptickmetachu deleted the release-please--branches--develop branch January 23, 2025 02:07
@github-actions
Copy link
Contributor Author

🤖 Created releases:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants