Developers using GitHub Sponsors now have the ability to control Custom Amounts on their Sponsors profile with more granularity. Users can enable Custom Amounts for use with a recurring sponsorship, a one-time sponsorship, both, or neither.
In June, we announced that security alert notifications are opt-in on a per-repository basis, using the repository's watch settings. Today, we have updated security alert digest emails to also respect these settings.
If you are no longer receiving digest emails for a repository and want to, please update your notification subscription settings on that repo to include Security Alerts.
You can now set an expiration date on your new and existing personal access tokens.
Setting an expiration date on personal access tokens is highly recommended as this helps keep your information secure. GitHub will send you an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving you a duplicate token with the same properties as the original.
When using a personal access token with the GitHub API, you'll see a new response header, GitHub-Authentication-Token-Expiration, indicating the token's expiration date. You can use this in scripts, for example to log a warning message as the expiration date approaches.
Learn more about personal access tokens and how to use them.