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

Implement auto-release, or document "use HEAD" dep? #17

Open
12wrigja opened this issue Mar 25, 2024 · 2 comments
Open

Implement auto-release, or document "use HEAD" dep? #17

12wrigja opened this issue Mar 25, 2024 · 2 comments

Comments

@12wrigja
Copy link
Collaborator

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?

@ptomato
Copy link
Collaborator

ptomato commented Mar 25, 2024

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.)

@justingrant
Copy link
Contributor

I admit I feel a little nervous about auto-release. Maybe hold off on automation and do the docs thing?

This was referenced Apr 4, 2024
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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants