Skip to content

x/pkgsite: automate fetching of new versions of Go standard library #37568

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
dmitshur opened this issue Feb 28, 2020 · 2 comments
Open

x/pkgsite: automate fetching of new versions of Go standard library #37568

dmitshur opened this issue Feb 28, 2020 · 2 comments
Labels
FeatureRequest Issues asking for a new feature that does not need a proposal. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. pkgsite
Milestone
pkgsite/unplanned

Comments

@dmitshur
Copy link
Member

This issue is related to #37002, but limited in scope to just the Go standard library.

When a new version of Go is released, it takes a manual action to add it to pkg.go.dev. This can and should be automated, so that it happens as soon as a new Go version is released.

/cc @julieqiu @jba @cagedmantis @toothrot @FiloSottile
@dmitshur dmitshur added FeatureRequest Issues asking for a new feature that does not need a proposal. pkgsite labels Feb 28, 2020
@dmitshur dmitshur added this to the Unreleased milestone Feb 28, 2020
@gopherbot gopherbot added the Documentation Issues describing a change to documentation. label Feb 28, 2020
@dmitshur dmitshur removed the Documentation Issues describing a change to documentation. label Feb 28, 2020
@gopherbot gopherbot added the Documentation Issues describing a change to documentation. label Feb 28, 2020
@dmitshur dmitshur removed the Documentation Issues describing a change to documentation. label Feb 28, 2020
@julieqiu julieqiu added the NeedsFix The path to resolution is known, but the work has not been done. label Feb 29, 2020
@dmitshur dmitshur mentioned this issue Feb 29, 2020
Open
@dmitshur
Copy link
Member Author

One of the ways this can be implemented is by using maintner to watch for when new Go release tags are pushed. I opened #37577 about potentially documenting that process so it's more discoverable.

@julieqiu julieqiu changed the title go.dev: automate fetching of new versions of Go standard library documentation go.dev: automate fetching of new versions of Go standard library Mar 12, 2020
@julieqiu julieqiu changed the title go.dev: automate fetching of new versions of Go standard library x/pkgsite: automate fetching of new versions of Go standard library Jun 15, 2020
@dmitshur dmitshur self-assigned this Aug 2, 2020
@dmitshur dmitshur added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. and removed NeedsFix The path to resolution is known, but the work has not been done. labels Aug 2, 2020
@dmitshur dmitshur removed their assignment Apr 4, 2022
@dmitshur
Copy link
Member Author

dmitshur commented Nov 4, 2022

In #56560, @hyangah makes this suggestion too and points out that by now we have relui. So this can also be implemented by adding a task in the relui release workflow that notifies pkg.go.dev about the new release. CC @golang/release.

@dmitshur dmitshur mentioned this issue Nov 4, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
FeatureRequest Issues asking for a new feature that does not need a proposal. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. pkgsite
Projects
None yet
Milestone
pkgsite/unplanned
Development

No branches or pull requests
4 participants
@dmitshur @julieqiu @gopherbot @dle8