The Wayback Machine - https://web.archive.org/web/20250423012358/https://github.blog/changelog/2025-04-22-dependabot-now-lets-you-schedule-update-frequencies-with-cron-expressions/

Dependabot now lets you schedule update frequencies with cron expressions

Dependabot users can now schedule custom update frequencies by using cron expressions in schedule.interval in the Dependabot configuration file. This enhances the predefined intervals (daily, weekly, and monthly) and provides a more generic and robust solution. This gives Dependabot users the ability to define custom schedules that meet their specific needs.

For help writing a cron expression, try this tool.

To learn more about using cron expressions to schedule Dependabot updates in the dependabot.yml file, check out GitHub’s Dependabot schedule.interval docs.

To engage with the Dependabot community on the topic of cron-based update scheduling, join the conversation.

New Changelog interface

What is changing?

We are excited to share that we have shipped a new UI for users who read through our changelogs on the GitHub blog webpage! This is meant to make your reading journey a lot more seamless by providing necessary contextual elements around each post.

Improvements
Deprecations

What exactly are the changes?

  • The overall look and feel of the UI now closely mirrors the experience that you get when you log into github.com.
  • You’ll see that new posts are categorized into one of three categories: New Release, Improvement, or Deprecation.
  • There is a new set of 12 curated categories that you can filter on to see changes by that product area.
  • We have introduced a new summarization feature to help assist quick consumption of content so you don’t have to read through each individual post (unless you want to!).
  • Posts are now grouped into months for easy viewing and archived into years for last referencing.

New curated label filters

Why is it important?

We heard your feedback that it can be hard to read through the latest changes and understand what changes are new features releases versus what are slight improvements to existing feature sets. We hope that this will make it clearer, and you will be able to filter on the curated, new feature categories that are most relevant for you. This will also enable you to catch up on all the changes of that category quicker, supported by our new summarization feature.

When is it changing?

The aforementioned changes will be in effect starting April 23, 2025. You may have already experienced this in its newest form!

See more

This is a follow-up to our previous announcement about npm replication APIs.

The new replication feed APIs are now live. While the legacy feeds will remain available—with limitations and scheduled brownout periods—until May 29, 2025, we strongly encourage all users to begin transitioning to the new APIs as soon as possible.

To access the updated feeds ahead of the deprecation, include the npm-replication-opt-in header with a value of true in your requests. This will route your traffic to the new APIs, bypassing the legacy feeds and avoiding any disruptions during brownout phases.

Please note that starting May 29, 2025, the legacy feeds will be fully deprecated. After this date, all requests to the replication feeds will automatically be served by the new APIs, regardless of header usage.

This change is part of our ongoing efforts to improve the performance and reliability of our services. We appreciate your understanding and cooperation during this transition.

Check out the migration guide and join the discussion in GitHub Community.

See more