Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Update docs to no longer update the npm-*.*.* and releases branches #610

Closed
JoshuaKGoldberg opened this issue Oct 29, 2018 · 1 comment
Closed

Update docs to no longer update the npm-*.*.* and releases branches #610

JoshuaKGoldberg opened this issue Oct 29, 2018 · 1 comment
Labels
Type: Question
Milestone
6.0.0-beta

Comments

@JoshuaKGoldberg
Copy link

Most other npm packages don't have the extra niceties. Do people actually use these?

/cc @HamletDRC
@HamletDRC
Copy link
Member

@JoshuaKGoldberg as long as the release process wiki page is up to date and we can make releases, then we're free to change it any way we want. So do what you want here.

@JoshuaKGoldberg JoshuaKGoldberg changed the title Question: do we still need to have npm-*.*.* and releases branches Update docs to no longer update the npm-*.*.* and releases branches Nov 1, 2018
JoshuaKGoldberg pushed a commit that referenced this issue Nov 2, 2018
Removed references to npm-*.*.* and releases branches from docs
3a917a3 
I'll also update the Releases wiki page to no longer suggest them.

Fixes #610
@JoshuaKGoldberg JoshuaKGoldberg mentioned this issue Nov 2, 2018
Merged
JoshuaKGoldberg pushed a commit that referenced this issue Nov 5, 2018
Removed references to npm-*.*.* and releases branches from docs (#626)
0d2b678 
I'll also update the Releases wiki page to no longer suggest them.

Fixes #610
@JoshuaKGoldberg JoshuaKGoldberg modified the milestones: None, 6.0.0-beta0 Nov 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Type: Question
Projects
None yet
Milestone
6.0.0-beta
Development

No branches or pull requests
2 participants
@HamletDRC @JoshuaKGoldberg