How should the changelog be updated if a change is backported from a newer branch to an older one?

Suppose I am developing an application with the following versions currently available: Latest stable: 1.3.0 Latest beta: 1.3.1 Latest alpha: 2.0.0 The project has a main branch for 2.x development and v1 for stable 1.x releases. I push a change to main and add it the changelog in main under 2.0.0 accordingly. Let's say I then backport a change from main that becomes part of the 1.3.1 release, and update the changelog in v1 under the new 1.3.1 section. Suppose version 2.0.0 is then released. How should I update the changelog in main in this case? Do I include the change under both 1.3.1 and 2.0.0 sections? Or do I move the change from 2.0.0 down to 1.3.1 because the latter came out first?

Jun 6, 2025 - 02:50
 0

Suppose I am developing an application with the following versions currently available:

  • Latest stable: 1.3.0
  • Latest beta: 1.3.1
  • Latest alpha: 2.0.0

The project has a main branch for 2.x development and v1 for stable 1.x releases. I push a change to main and add it the changelog in main under 2.0.0 accordingly. Let's say I then backport a change from main that becomes part of the 1.3.1 release, and update the changelog in v1 under the new 1.3.1 section. Suppose version 2.0.0 is then released.

How should I update the changelog in main in this case? Do I include the change under both 1.3.1 and 2.0.0 sections? Or do I move the change from 2.0.0 down to 1.3.1 because the latter came out first?