-
Notifications
You must be signed in to change notification settings - Fork 3
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
Implement auto-release, or document "use HEAD" dep? #17
Comments
No preference. Probably documenting how to depend on the repo directly is the least hassle (and doesn't involve needing to add and remove people as NPM maintainers.) |
I admit I feel a little nervous about auto-release. Maybe hold off on automation and do the docs thing? |
ptomato
added a commit
to tc39/proposal-temporal
that referenced
this issue
Apr 30, 2024
This package is switching to a 'use the repo directly' workflow. See js-temporal/temporal-test262-runner#17
Ms2ger
pushed a commit
to tc39/proposal-temporal
that referenced
this issue
May 2, 2024
This package is switching to a 'use the repo directly' workflow. See js-temporal/temporal-test262-runner#17
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given there are so few commits to this repo, I'm wondering if it makes sense for most users to depend on the HEAD / latest version of this repo in one of a couple ways:
Thoughts?
The text was updated successfully, but these errors were encountered: