v1.1.0: Major dependency upgrade, labels support, and Probot v13 fix

Highlights

• Discussion labels support — You can now add labels to created discussions using comma-separated or YAML array syntax in your announcement config (#108)
• Major dependency upgrade — Updated Node.js to v22 LTS, Probot v12→v13, @azure/cosmos v3→v4, TypeScript v5.8, ESLint v9 (flat config), and replaced crypto-js with native Node.js crypto (resolves all npm audit vulnerabilities) (#107)
• OIDC authentication for deployments — CI/CD workflows now use federated credentials instead of secrets (#107)
• What-If PR comments — Infrastructure PRs now show Azure What-If deployment results as sticky comments (#107)

Bug Fixes

• Fix webhook 404s after Probot v13 upgrade by setting WEBHOOK_PATH=/ (#109)
• Fix GitHub Actions multi-line output delimiter handling in Azure deployment
• Fix remoteDebuggingVersion from VS2019 to VS2022 in Bicep
• Fix token deletion timing in non-prod mode

DevOps

• Separate concurrency groups for infrastructure and app deployments
• Add automated e2e test script and updated testing docs
• Upgrade ESLint to v9 with flat config (eslint.config.mjs)

Full Changelog: v1.0.5...v1.1.0

v1.0.5: Fix repo discussion categories

There was a bug where repo discussions with more than 10 discussion categories were not able to find the category to create the post with. I fixed that 🎉 I also took the opportunity to upgrade the node version and all the packages.

What's Changed

• Upgrade node, typescript, packages, fix bugs by @philip-gai in #99

Full Changelog: v1.0.4...v1.0.5

v1.0.4

What's Changed

• Fix errors causing the bot to comment on the PR more than once
• Update wording and formatting of the PR comments
• Display a more helpful message when the bot cannot find a private repository because it is not installed on it

Full Changelog: v1.0.3...v1.0.4

v1.0.3: Better Auth UX and More

What's Changed

• Once a user has successfully authorized the GitHub app, they will see a success screen and then will get automatically redirected back to their pull request.
• We are now using the state parameter when auth'ing with an encrypted value to protect against forgery attacks and to pass along the pull request url.
• The wording on the PR comment has been updated to say "authorize the app" instead of "authenticate".

Links

• UX and security enhancements by @philip-gai in #82

Full Changelog: v1.0.2...v1.0.3

v1.0.2: Link to PR from Discussions and more

What's Changed

• Calculate the header end line by @philip-gai in #79
• Add link to public PRs in the discussion footer by @philip-gai in #80
• Add FAQ to README by @philip-gai in #81

Full Changelog: v1.0.1...v1.0.2

v1.0.1: Remove reaction approval

Removing the need to react to the bot comment with a 🚀 to approve the discussion to be posted. This is an unnecessary precaution.

What's Changed

• Remove reaction approval by @philip-gai in #77

Full Changelog: v1.0.0...v1.0.1

v1.0.0: Official Release

Now that resync and other features are complete, releasing v1 🎉

Full Changelog: v0.15.0...v1.0.0

v0.15.0: Smart Sync and More

Smart Sync

Announcement Drafter just got a whole lot smarter. Now, when you push new commits or reopen a pull request, the announcement drafter will revalidate your markdown. This means no more messing up the header and having to recreate the PR! 🎉

Also, if your PR is a draft then the announcement drafter will leave you alone. Once you mark it as ready for review, then the announcement drafter will take a 👀.

Removing the author setting

You used to have to specify the author of the post in the markdown header, like this:

<!--
author: philip-gai
repository: https://github.com/philip-gai/announcement-drafter-demo
category: announcements
-->

But now you don't need to. The announcement drafter will assume whoever created the PR should be the author of the discussion. So now the markdown header would just be:

<!--
repository: https://github.com/philip-gai/announcement-drafter-demo
category: announcements
-->

What's Changed

• Smart synchronize and (couldn't help myself) more cleanup by @philip-gai in #74
  Full Changelog: v0.14.0...v0.15.0

v0.14.0

What's Changed

• Get author login from pull request author and setup dev loop by @philip-gai in #73

Full Changelog: v0.13.0...v0.14.0

v0.13.0

Add nbsp after the heart in the footer

It looked weird before