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

Use correct package ranges in create recipes #1214

Merged
merged 1 commit into from
Feb 25, 2025
Merged

Conversation

scotttrinh
Copy link
Collaborator

We should consider using a more robust way of managing these ranges to avoid needing to always touch these directly, while also avoiding making them roughly "*".

This only "broke" because we don't have these old versions published and ^ for 0.x versions won't automatically install the latest minor version since that's considered a breaking change.

We should consider using a more robust way of managing these
ranges to avoid needing to always touch these directly, while also
avoiding making them roughly "*".
@scotttrinh scotttrinh enabled auto-merge (squash) February 25, 2025 03:13
@scotttrinh scotttrinh disabled auto-merge February 25, 2025 03:27
@scotttrinh scotttrinh merged commit a1217c0 into master Feb 25, 2025
9 checks passed
@scotttrinh scotttrinh deleted the fix-package-ranges branch February 25, 2025 03:27
@diksipav
Copy link
Contributor

I also wanted to ask when is going to be the right time to publish 1.0.0 versions of auth packages? They seem stable enough. Are we going to add more features soon?

@scotttrinh
Copy link
Collaborator Author

I also wanted to ask when is going to be the right time to publish 1.0.0 versions of auth packages? They seem stable enough. Are we going to add more features soon?

I have a small number of breaking changes in mind that I haven't had time to really design. We also need to have a lot more documentation and examples. Hopefully soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants