List view
- No due date
- No due date•1/7 issues closed
- Due by April 24, 2026•0/16 issues closed
We can close this milestone when the output of the generator for `secretmanager-v1` is of sufficient quality to create a release. This is a good milestone to record "before GA but after MVP" items, such as: - The generated documentation comments are correct and readable. - The generated code has good examples. - The generated code includes pagination and LRO helpers. - The generated code has configuration parameters for retry and polling loops.
No due date•0/3 issues closedWe can close this milestone when the generator produces working code for `google-cloud-secretmanager-v1`. That is, the generated code must compile and we must be able to write integration tests. There are external (to librarian) dependencies such as the well-know types, a gax library, etc.
No due date•0/2 issues closedTo close this PR we should demonstrate that `librarian generate` produces a library for `google/cloud/security/publicca/v1`. In addition to the functionality from "[1] Swift: ...." the library should now be able to send an HTTP request for the one service (and one RPC) in this API. The RPC should: - Allow callers to set the request parameters. - If successful, parse the HTTP response and return that to the caller. - If failed, raise some (unspecified) error type. **Out of scope:** parsing the error types **Out of scope:** implementing a retry loop **Out of scope:** implementing pagination (the service does not have them). **Out of scope:** implementing LROs (the service does not have them).
No due date•3/7 issues closed- Due by April 24, 2026•1/3 issues closed
- Due by April 24, 2026•0/9 issues closed
- Due by April 24, 2026•0/13 issues closed
- No due date•0/2 issues closed
- No due date•1/2 issues closed
- No due date•0/28 issues closed
- Due by April 10, 2026•19/27 issues closed
- No due date•0/8 issues closed
- Due by April 24, 2026•1/8 issues closed
- No due date
- No due date•1/10 issues closed
- No due date•0/1 issues closed
- Due by April 10, 2026•16/31 issues closed
- No due date•2/7 issues closed
- No due date
- Due by April 10, 2026•45/55 issues closed
- No due date•8/32 issues closed
Migrate Python from legacylibrarian generate to librarian generate
Due by April 10, 2026•50/52 issues closed- No due date•9/15 issues closed
Design and implement a clear source of truth for every aspect of configuration
No due date•1/7 issues closedAny issue that hasn't been prioritized yet for surfer project.
No due date•29/67 issues closed- No due date•26/65 issues closed
Changes that need to be made to the Librarian CLI in order to support IBV. See go/sdk:client-ibv for more details
Due by April 10, 2026•17/22 issues closed- Due by April 10, 2026•27/37 issues closed
These are any tickets that should be looked into to support existing customers.
No due date•138/143 issues closedBucket 3: Items Requiring Broad Alignment & Org-Wide Rollout These are large-scale initiatives affecting all repositories and teams, requiring a clear communication and phased rollout plan.
No due date•4/24 issues closedBucket 2: Items Requiring Design & Project Work These items require dedicated design, discussion, and prototyping before org-wide implementation.
No due date•0/13 issues closedWe plan to deprecate/migrate bots in https://github.com/googleapis/repo-automation-bots as part of the librarian project. This milestone tracks progress towards that work. This milestones contains bots that are ready to start deprecation. Plan to follow the bot deprecation framework: go/cloud-sdk-bot-deprecation-framework
No due date•51/69 issues closedWork that has been triaged but not yet planned. This milestone is used to distinguish it from untriaged issues, which will have no milestone assigned.
No due date•108/128 issues closed