Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Incorrect versions/tags on NPM and docs site?

See original GitHub issue

AFAICT, v6.0.0-beta.2 is currently the latest and greatest, though I’m a bit confused. 10 months ago, v6.0.0 was published to NPM: https://www.npmjs.com/package/ember-intl/v/6.0.0

And the docs site even includes v6.0.1: https://ember-intl.github.io/ember-intl/versions/v6.0.1/

Issue Analytics

State:
Created 2 years ago
Reactions:4
Comments:14 (10 by maintainers)

Top GitHub Comments

3reactions

buschtoenscommented, Jan 19, 2022

I think we need to do these things:

Properly release v6.x and tag it as latest on npm, e.g. v6.1.0.
- Are there any outstanding issues / incompatibilities / tasks that would prevent a proper v6.x release? Edit: yes
  - CI is broken
  - …more?
- Do we want to include more breaking changes?
Check wehther we should deprecate any versions from npm.
- e.g. v6.0.0
- If v5.7.1 & v5.7.2 indeed include v6.x breaking changes, we should consider deprecating them, once v6.x is released and tagged as latest. However, we must evaluate, whether by doing so we risk breaking apps of users who already upgraded to these versions vs. whether there’s actually any real danger for users unwittingly installing these v6.x changes.
To prevent future mistakes:
- Create a RELEASING.md
- Or even better yet, we could setup a fully automated releases process. @Turbo87 recently did this in one of my packages and AFAICT it’s working really great: https://github.com/buschtoens/ember-link/pull/674

2reactions

gzurbachcommented, Jan 20, 2022

@buschtoens Thank you for looking into this and sending all these details. I don’t think I have the skills to help, but I’m impressed and supportive of your efforts to fix this 👍

Top Results From Across the Web

Common errors | npm Docs

Possible temporary npm registry glitch, or corrupted local server cache. Run npm cache clean and/or try again later. · This can be caused...

npm-version - npm Docs

Default: true; Type: Boolean. Tag the commit when using the npm version command. Setting this to false results in no commit being made...

npm-dist-tag

npm -dist-tag. Modify package distribution tags. Select CLI Version: Version 9.2.0 (Latest Release).

npm-install - npm Docs

npm install node-tap --save-dev ... See the git man page for details. Examples: ... Will also prevent writing to package-lock.json if set to...

go-coin module - github.com/coin-labs/go-coin - Go Packages

Project Layout · daemon/algod holds the algod daemon, which implements a participating node. algod allows a node to participate in the agreement protocol,...