Summary

Cutting a release in drivers-evergreen-tools or drivers-github-tools creates a GitHub release, but nothing tells contributors to announce it. Add a note to each repo's CONTRIBUTING.md: after cutting a release, post the new version and what changed to #client-libraries on Slack.

Motivation

Who is the affected end user?

Contributors who cut releases in these repos, and the teams that consume the tools, mainly driver maintainers and DevProd.

How does this affect the end user?

Releases land without announcement. Teams that depend on the scripts and actions learn about new versions late or never.

How likely is it that this problem or use case will occur?

Every release.

If the problem does occur, what are the consequences and how severe are they?

Minor annoyance: missed communication. No functional impact.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

No. It is a documentation change.

Acceptance Criteria

• The Releasing section of drivers-evergreen-tools' CONTRIBUTING.md says to announce the new release version and what changed in #client-libraries.
• The same note exists in drivers-github-tools' CONTRIBUTING.md.