How come npmjs website shows that Truffle latest version is 4.1.14, and that it was published 3 days ago?
up vote
1
down vote
favorite
According to this page, Truffle latest version is 4.1.14, and it was published 3 days ago.
However:
- I have been using this version for months now.
- I have noticed this "published 3 days ago" several times before (more than 3 days ago).
- This version works in conjunction with solc v0.4.24, and I have encountered several questions here about using Truffle in order to test contracts compiled with Solidity v0.5.0.
Can somebody please explain what exactly is going on here, and what is the current latest version of Truffle?
Thanks
truffle solc compilation
add a comment |
up vote
1
down vote
favorite
According to this page, Truffle latest version is 4.1.14, and it was published 3 days ago.
However:
- I have been using this version for months now.
- I have noticed this "published 3 days ago" several times before (more than 3 days ago).
- This version works in conjunction with solc v0.4.24, and I have encountered several questions here about using Truffle in order to test contracts compiled with Solidity v0.5.0.
Can somebody please explain what exactly is going on here, and what is the current latest version of Truffle?
Thanks
truffle solc compilation
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
According to this page, Truffle latest version is 4.1.14, and it was published 3 days ago.
However:
- I have been using this version for months now.
- I have noticed this "published 3 days ago" several times before (more than 3 days ago).
- This version works in conjunction with solc v0.4.24, and I have encountered several questions here about using Truffle in order to test contracts compiled with Solidity v0.5.0.
Can somebody please explain what exactly is going on here, and what is the current latest version of Truffle?
Thanks
truffle solc compilation
According to this page, Truffle latest version is 4.1.14, and it was published 3 days ago.
However:
- I have been using this version for months now.
- I have noticed this "published 3 days ago" several times before (more than 3 days ago).
- This version works in conjunction with solc v0.4.24, and I have encountered several questions here about using Truffle in order to test contracts compiled with Solidity v0.5.0.
Can somebody please explain what exactly is going on here, and what is the current latest version of Truffle?
Thanks
truffle solc compilation
truffle solc compilation
asked 7 hours ago
goodvibration
2,360721
2,360721
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
The "3 days ago" is version agnostic: it just means the package, regardless of version, was last updated then.
If you look at the version history tab (the purple tab on the right):
Version History
5.0.0-next.18 ...... 3 days ago
5.0.0-beta.2 ..... 12 days ago
...
You'll also notice that the tagged latest
version is 4.1.14
, whereas all 5.0
releases are tagged otherwise (e.g. beta
):
Current Tags
4.1.14 ........... latest
5.0.0-beta.2 ..... beta
So the last stable release is 4.1.14
, but other beta releases have been made since then, hence the "3 days ago" thing.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
The "3 days ago" is version agnostic: it just means the package, regardless of version, was last updated then.
If you look at the version history tab (the purple tab on the right):
Version History
5.0.0-next.18 ...... 3 days ago
5.0.0-beta.2 ..... 12 days ago
...
You'll also notice that the tagged latest
version is 4.1.14
, whereas all 5.0
releases are tagged otherwise (e.g. beta
):
Current Tags
4.1.14 ........... latest
5.0.0-beta.2 ..... beta
So the last stable release is 4.1.14
, but other beta releases have been made since then, hence the "3 days ago" thing.
add a comment |
up vote
3
down vote
accepted
The "3 days ago" is version agnostic: it just means the package, regardless of version, was last updated then.
If you look at the version history tab (the purple tab on the right):
Version History
5.0.0-next.18 ...... 3 days ago
5.0.0-beta.2 ..... 12 days ago
...
You'll also notice that the tagged latest
version is 4.1.14
, whereas all 5.0
releases are tagged otherwise (e.g. beta
):
Current Tags
4.1.14 ........... latest
5.0.0-beta.2 ..... beta
So the last stable release is 4.1.14
, but other beta releases have been made since then, hence the "3 days ago" thing.
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
The "3 days ago" is version agnostic: it just means the package, regardless of version, was last updated then.
If you look at the version history tab (the purple tab on the right):
Version History
5.0.0-next.18 ...... 3 days ago
5.0.0-beta.2 ..... 12 days ago
...
You'll also notice that the tagged latest
version is 4.1.14
, whereas all 5.0
releases are tagged otherwise (e.g. beta
):
Current Tags
4.1.14 ........... latest
5.0.0-beta.2 ..... beta
So the last stable release is 4.1.14
, but other beta releases have been made since then, hence the "3 days ago" thing.
The "3 days ago" is version agnostic: it just means the package, regardless of version, was last updated then.
If you look at the version history tab (the purple tab on the right):
Version History
5.0.0-next.18 ...... 3 days ago
5.0.0-beta.2 ..... 12 days ago
...
You'll also notice that the tagged latest
version is 4.1.14
, whereas all 5.0
releases are tagged otherwise (e.g. beta
):
Current Tags
4.1.14 ........... latest
5.0.0-beta.2 ..... beta
So the last stable release is 4.1.14
, but other beta releases have been made since then, hence the "3 days ago" thing.
edited 6 hours ago
answered 6 hours ago
Richard Horrocks
20.8k94499
20.8k94499
add a comment |
add a comment |
Thanks for contributing an answer to Ethereum Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fethereum.stackexchange.com%2fquestions%2f63483%2fhow-come-npmjs-website-shows-that-truffle-latest-version-is-4-1-14-and-that-it%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown