CHANGELOG.md was not updated after v1.86.0 release.

Open
#13,177 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, java, yaml
Domain
ci-cd, release

Research direction

Start with .github/workflows/changelog_generation.yaml and compare its post-migration paths and triggers with the v1.86.0 release. Check java-spanner/CHANGELOG.md against the release notes, then inspect or run the workflow to identify why the split was skipped. Done means the workflow updates each affected library's CHANGELOG.md after a release.

Written by the indexing model from the issue text.

Description

There is a changelog generation workflow that is supposed to split the release notes from main to CHANGELOG.md in each individual libraries.
However, it stopped working since monorepo migration. For example, CHANGELOG.md in java-spanner was not updated after v1.86.0 release.

Dominant language
Java
Stars
2.1k
Forks
1.2k
Avg merge
2d 14h
Merged PRs (30d)
192

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-cloud-java

All issues in googleapis/google-cloud-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.