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

Installation instructions missing for the latest releases #171

Open
fgiloux opened this issue Sep 19, 2023 · 3 comments
Open

Installation instructions missing for the latest releases #171

fgiloux opened this issue Sep 19, 2023 · 3 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

Comments

@fgiloux
Copy link

fgiloux commented Sep 19, 2023

Under quick start:
install catalogd, navigate to the releases page, and follow the install instructions included in the release you want to install.

In the releases page there are instructions for v0.4.1 but nothing for the two latest releases v0.5.0 and v0.6.0.

@joelanford
Copy link
Member

Oh good catch. It looks like we have inconsistent release processes.

  • Anik and I may have used the GH UI to create the tag and auto-generate the release for 0.5.0 and 0.6.0.
  • However, we have a goreleaser config that creates the GH release (e.g. for 0.4.1) as part of the release workflow for tags.

Looks like one option is to use mode: replace in the goreleaser release configuration:

release:
  # What to do with the release notes in case there the release already exists.
  #
  # Valid options are:
  # - `keep-existing`: keep the existing notes
  # - `append`: append the current release notes to the existing notes
  # - `prepend`: prepend the current release notes to the existing notes
  # - `replace`: replace existing notes
  #
  # Default is `keep-existing`.
  mode: replace

@joelanford joelanford added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Sep 20, 2023
@LalatenduMohanty
Copy link
Member

I checked the recent releases and did not find the issue. Looks like it is fixed somehow?

@joelanford
Copy link
Member

@LalatenduMohanty I think it depends on how the tag appears.

If someone pushes a tag, the release works as expected.
If someone creates a release via the GH UI, the goreleaser release fails because the release already exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

3 participants