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): release 0.11.0 #158

Merged
merged 1 commit into from
Aug 6, 2024
Merged

Conversation

fredrikaverpil
Copy link
Owner

🤖 I have created a release beep boop

0.11.0 (2024-08-01)

Features


This PR was generated with Release Please. See documentation.

@fredrikaverpil fredrikaverpil force-pushed the release-please--branches--main branch from 7d9e8e1 to 7496edf Compare August 1, 2024 20:20
@fredrikaverpil
Copy link
Owner Author

fredrikaverpil commented Aug 2, 2024

@mrcjkb I'm just waiting for #156 to be verified and merged before releasing this and we should have the adapter released on luarocks.

@fredrikaverpil fredrikaverpil merged commit dddd1c1 into main Aug 6, 2024
9 checks passed
@fredrikaverpil fredrikaverpil deleted the release-please--branches--main branch August 6, 2024 14:47
@fredrikaverpil
Copy link
Owner Author

🤖 Created releases:

@fredrikaverpil
Copy link
Owner Author

fredrikaverpil commented Aug 6, 2024

@mrcjkb I think it might take some time until that PR gets merged, so I just released now which should publish to luarocks.

EDIT: I guess it worked: https://luarocks.org/modules/fredrikaverpil/neotest-golang
Here's the action output: https://github.com/fredrikaverpil/neotest-golang/actions/runs/10268804156/job/28412701146
It mentions 0.11.0 already existing, hence 0.11.0-1... 🤔
I added the neovim label to the package over at luarocks.

@mrcjkb
Copy link
Contributor

mrcjkb commented Aug 6, 2024

Yep, looks good 🎉

It mentions 0.11.0 already existing, hence 0.11.0-1... 🤔

That's because the workflow triggers on both releases and on tags (-1 is just a luarocks thing, called specrev. All packages have one).
By default, it aborts the upload without an error if the package already exists (there's a fail_on_duplicate flag to change that behaviour).

@fredrikaverpil
Copy link
Owner Author

Awesome! 😊

Hm. I feel like I would like to include in the README how to install using this method. I currently only have Lazy as an installation example.

@mrcjkb would you be up for contributing with an example in the README?

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