Updating github changes command in post release workflow (changelog fix)

[KasukabeDefenceForce]

:pencil: Description

Type: :beetle: bugfix | :rocket: feature | :biohazard: breaking change | :vertical_traffic_light: testing | :memo: documentation | :roller_coaster: infrastructure

Fixing the post release workflow by updating the github changes command.

Also, link issues affected by this pull request by using the keywords: close, closes, closed, fix, fixes, fixed, resolve, resolves or resolved.

:pushpin: Resources

Examples, notebooks, and links to useful references.

:vertical_traffic_light: Testing

How did you test these changes?

• [ ] Testing pipeline
• [ ] Other method (describe)
• [ ] My changes can't be tested (explain why)

:ballot_box_with_check: Checklist

• [ ] I requested two reviewers for this pull request
• [ ] I updated the documentation according to my changes
• [ ] I built the documentation by applying the build_docs label

Note: If you are not allowed to perform any of these actions, ping (@) a contributor.

[andrewfullard]

Can you provide an example changelog entry?

[KasukabeDefenceForce]

Can you provide an example changelog entry?

https://github.com/KasukabeDefenceForce/tardis/actions/runs/9645564434

[andrewfullard]

Can you provide an example changelog entry?

https://github.com/KasukabeDefenceForce/tardis/actions/runs/9645564434

Looks good, I assume the missing version and incorrect date is because it's not attached to an actual release?

[KasukabeDefenceForce]

Can you provide an example changelog entry?

https://github.com/KasukabeDefenceForce/tardis/actions/runs/9645564434

Looks good, I assume the missing version and incorrect date is because it's not attached to an actual release?

Yes