Once librarian is used for generate in bot Go & Python, we no longer need any cloud infrastructure for legacylibrarian generate, nor do we need the corresponding automation configuration (see #5242 for Python disablement).
Furthermore, since librarian is currently operated by a human for various steps, including generate, we are going to move release staging to human operation as well. As such, we are pausing the legacylibrarian release stage cron jobs for both languages. When we are sure we no longer need these jobs at all, we can clean up the infrastructure.
Important: The legacylibrarian release publish jobs must be retained until a complete librarian-based release design is finalized.
Once
librarianis used for generate in bot Go & Python, we no longer need any cloud infrastructure forlegacylibrarian generate, nor do we need the corresponding automation configuration (see #5242 for Python disablement).Furthermore, since
librarianis currently operated by a human for various steps, includinggenerate, we are going to move release staging to human operation as well. As such, we are pausing thelegacylibrarian release stagecron jobs for both languages. When we are sure we no longer need these jobs at all, we can clean up the infrastructure.Important: The
legacylibrarian release publishjobs must be retained until a completelibrarian-based release design is finalized.