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(release): 0.1.0 #1

Merged
merged 1 commit into from
Dec 30, 2023
Merged

chore(release): 0.1.0 #1

merged 1 commit into from
Dec 30, 2023

Conversation

release-please-nobbs[bot]
Copy link
Contributor

@release-please-nobbs release-please-nobbs bot commented Dec 30, 2023 •
edited
Loading

🤖 I have created a release beep boop

0.1.0 (2023-12-30)

Build System

  • fix go version in go.mod (471b8db)

Miscellaneous Chores

Continuous Integration

  • add build on release (763f003)
  • build: disable CGO (1608ca2)
  • build: multi-arch and multi-os build (2ff900b)
  • build: overwrite release assets (de50d0c)

Features

  • initial implementation of ticket list command (8043689)

This PR was generated with Release Please. See documentation.

@release-please-nobbs release-please-nobbs bot force-pushed the release-please--branches--main branch 7 times, most recently from 3133c6a to 602321a Compare December 30, 2023 11:21
@nobbs nobbs merged commit 16659fe into main Dec 30, 2023
6 checks passed
@release-please-nobbs Release Please (@nobbs)
Copy link
Contributor Author

🤖 Release is at https://github.com/nobbs/kubectl-mapr-ticket/releases/tag/v0.1.0 🌻

@nobbs nobbs deleted the release-please--branches--main branch December 30, 2023 18:20
@nobbs nobbs restored the release-please--branches--main branch December 30, 2023 18:20
@nobbs nobbs deleted the release-please--branches--main branch December 30, 2023 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
autorelease: tagged
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@nobbs