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

Flakestry releases #4974

Open
felschr opened this issue Jan 29, 2024 · 3 comments
Open

Flakestry releases #4974

felschr opened this issue Jan 29, 2024 · 3 comments

Comments

@felschr
Copy link

felschr commented Jan 29, 2024

Description

It would be really cool for home-manager to be on Flakestry.

It's a registry for flakes that supports semantic versioning.

Here is the announcement post in the NixOS forum:
https://discourse.nixos.org/t/announcing-flakestry-dev-new-registry-for-flakes/34583

Publishing rolling releases (for master) would currently be blocked by flakestry/flakestry.dev#35. However it looks like it'll be merged soon.

@felschr felschr changed the title Flakestry release Flakestry releases Jan 29, 2024
@eclairevoyant
Copy link

Do they really support semver yet? Seems not based on flakestry/flakestry.dev#41.

Also not sure I see the benefit of "semver" for non-tagged repos.

@felschr
Copy link
Author

felschr commented Feb 6, 2024

Oh, you're right. It's only mentioned in the roadmap in the README.md. My bad.

Copy link

stale bot commented May 9, 2024

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

  • If this is resolved, please consider closing it so that the maintainers know not to focus on this.
  • If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

  • If you are also experiencing this issue, please add details of your situation to help with the debugging process.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

@stale stale bot added the status: stale label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants