question-mark
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.

Link to "What changed since the previous release?"

See original GitHub issue

Issuehunt badges

Example: https://github.com/parcel-bundler/parcel/releases

Can you tell what each release includes? GitHub links to the tagged commit but that’s rather useless

Wouldn’t it make sense to list the commits between each tag/release (in chronological order).

This is the link that should appear on v1.4.1: https://github.com/parcel-bundler/parcel/compare/v1.4.0...v1.4.1

Without any fetches we can show the link on

hardikmodha earned $80.00 by resolving this issue!

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:14
  • Comments:25 (23 by maintainers)

github_iconTop GitHub Comments

1reaction
fregantecommented, Apr 28, 2019

Ok, then only fetch that page: https://github.com/parcel-bundler/parcel/releases?after=parcel-bundler@1.12.3

  • ignore the pagination in it, let’s not add prev/next for now
  • if you want to add prefix-aware links (@parcel/integration-tests@***), only look in that page. If none are found, ignore the tag or just use the previous non-prefix-aware tag

If we really want to add a Next link we need to find a solution that does not require multiple consecutive fetches (whether it’s the pagination link or the brute force). But for now we can ignore it

1reaction
fregantecommented, Apr 28, 2019

One thing to keep in mind is, as seen on the parcel repo, they have multiple tags on the same commit, so “the previous tag” is not necessarily “the one below it”.

If not too complex (and if this is a standard many repos follow), there could be smart specific links like

  • parcel-bundler@1.12.2...parcel-bundler@1.12.3 on parcel-bundler tags
  • @parcel/integration-tests@1.12.2...@parcel/integration-tests@1.12.3 on @parcel/integration-tests tags

If too complex, it should at least make sure “the previous tag” doesn’t point to the same commit. e.g.

  • parcel-bundler@1.12.3...@parcel/integration-tests@1.12.3 (both are on 09c1082)
Read more comments on GitHub >

github_iconTop Results From Across the Web

Find what's changed in a file - Google Docs Editors Help
You can see changes that have been made to a document in Google Docs, Sheets, ... To return to the original current version,...
Read more >
Committing a change on a previous release version on master
Once it's ready to ship, the release branch gets merged into master and tagged with a version number. The point is: even if...
Read more >
Keep a Changelog
Version 1.0.0 # Changelog All notable changes to this project will be documented in this file. ... Links to latest released version in...
Read more >
Linking to releases - GitHub Docs
On GitHub.com, navigate to the main page of the repository. To the right of the list of files, click Releases. Releases section in...
Read more >
View the version history of an item or file in a list or library
The choices change based on whether you selected the latest file, or an earlier version. The version history window for the most recent...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found