Webhook delivery logs will only be retained for 3 days

Webhook delivery logs are now only retained for 3 days. For up to 3 days after a webhook delivery is posted, you can view details about that delivery and request a redelivery. For GitHub Enterprise Server instances, the retention period is still 7 days.

Learn more about viewing webhook deliveries and redelivering webhook deliveries.

Redesigned Navigation Now Available to All Users

The redesigned GitHub navigation is now live for everyone! After a successful beta phase, which allowed users to test and provide feedback, we’re confident in providing a more intuitive, responsive, and accessible navigation experience to all users by default.

Image of the new global navigation

Key Features & Improvements:

  • Efficient Breadcrumbs: Navigate with a clear understanding of your location on GitHub.
  • Streamlined Menus: New menus facilitate quick access to top repositories, teams, and common workflows. Just click the menu icon on the upper-left to access the global menu, or your user profile for the user menu.
  • Built for Search: Optimized navigation for new code search experiences, inclusive of a quick-access button for the command palette.
  • Enhanced Accessibility: Navigate seamlessly using any device and assistive technology.
  • Direct Links: Immediate access to a users entire collection of ‘issues’ and ‘pull requests’ across GitHub are availabel at the upper level of the navigation.
  • Mobile & Responsive Enhancements: Improved experiences on various screen sizes and devices.
  • Bug and Accessibility Fixes: Resolved issues to refine user interaction and accessibility.

Your Feedback Matters:

Your insights during the beta were invaluable. Thank you for helping us enhance GitHub. Explore and enjoy the refreshed navigation experience!

See more

Actions – Prevent self-reviews for secure deployments across Actions environments

Actions environments now makes it more secure to review and control deployments using manual approvals.

Previously, any user could trigger a workflow and also manually approve/reject a deployment job targeting a protected environment, if they are a required reviewer.

We are now introducing an option for environment admins to prevent required reviewers from self-reviews to secure deployments targeting their critical environments.
This would enforce that a different reviewer could approve and sign off the deployments, rather than the same user who triggered the run – making the deployments more secure.
Prevent self-reviews

Learn more about securing environments using deployment protection rules.
For questions, visit the GitHub Actions community.
To see what's next for Actions, visit our public roadmap.

See more
View all changes