I could be wrong, but I think before 5.0 when running an Update AL-Go System Files action, not only AL-Go, but also the RELEASENOTES.copy.md was updated. This is not happening (anymore?) for our Repos. As I said, I could be wrong... or maybe this is intentional. It was quite useful for our developers to quickly see which AL-Go version they have in their Repo and since the RELEASENOTES.copy.md always contains very useful information about new / deprecated features, it was good to have a current version in each repo.
Is there a way to get this updated when AL-Go is updated?
I could be wrong, but I think before 5.0 when running an Update AL-Go System Files action, not only AL-Go, but also the RELEASENOTES.copy.md was updated. This is not happening (anymore?) for our Repos. As I said, I could be wrong... or maybe this is intentional. It was quite useful for our developers to quickly see which AL-Go version they have in their Repo and since the RELEASENOTES.copy.md always contains very useful information about new / deprecated features, it was good to have a current version in each repo.
Is there a way to get this updated when AL-Go is updated?