Show the latest version on the landing page? #577

Activity

1. jgeewax

   added

   enhancement

   type: questionRequest for information or clarification. Not an issue.Request for information or clarification. Not an issue.

   docs

   on May 10, 2015
2. jgeewax

   added this to the Core Future milestone on May 10, 2015
3. ryanseys commented on May 11, 2015

   

   ryanseys

   on May 11, 2015

   Contributor

   More actions

   Latest npm version and date of that version push seems like a good idea. Any idea where on the landing page it seems most appropriate?
4. jgeewax commented on May 11, 2015

   

   jgeewax

   on May 11, 2015

   ContributorAuthor

   More actions

   I think it might look best somewhere at the top in the blue area?

   Maybe small text after gcloud? Or below the npm install --save gcloud ?

   @chriscalo any thoughts?
5. ryanseys

   closed this as completedin #611on May 19, 2015
6. JustinBeckwith

   assigned

   ryanseys

   on Feb 1, 2021
7. chingor13

   added 3 commits that reference this issue on Aug 22, 2022

   docs(samples): add example tags to generated samples (#577)

   ...

   2384cc3

   docs(samples): add example tags to generated samples (#577)

   ...

   ff7cd6f

   docs(samples): add example tags to generated samples (#577)

   ...

   e7ca14a
8. sofisl

   added a commit that references this issue on Sep 15, 2022

   chore(deps): update dependency linkinator to v4 (#577)

   ...

   e21bf76
9. sofisl

   added 2 commits that reference this issue on Sep 27, 2022

   fix(deps): google-gax v2.17.1 (#577)

   6a01032

   chore: release 3.3.6 (#578)

   ...

   5ed9386
10. sofisl

    added a commit that references this issue on Oct 11, 2022

    chore(deps): update dependency @types/node to v14 (#577)

    ...

    05358f6
11. 14 remaining items

    Load more
12. sofisl

    added 2 commits that reference this issue on Jan 27, 2026

    chore: run continuous and presubmit e2e tests in zone not used by oth…

    ...

    0a95431

    chore: run continuous and presubmit e2e tests in zone not used by oth…

    ...

    001f530
13. GautamSharda

    added a commit that references this issue on Feb 5, 2026

    chore: Report warning on `.github/workflows/ci.yaml` (#577)

    ...

    9b904bd
14. GautamSharda

    added a commit that references this issue on Feb 23, 2026

    chore: Report warning on `.github/workflows/ci.yaml` (#577)

    ...

    1840cbe
15. sofisl

    added a commit that references this issue on Feb 24, 2026

    Release v1.1.0 (#577)

    b522b89
16. GautamSharda

    added a commit that references this issue on Feb 26, 2026

    chore: Report warning on `.github/workflows/ci.yaml` (#577)

    ...

    a7f44e6
17. sofisl

    added a commit that references this issue on Feb 26, 2026

    fix(deps): update dependency arrify to v2 (#577)

    e41957e
18. GautamSharda

    added 3 commits that reference this issue on Mar 5, 2026

    chore(deps): update dependency @google-cloud/pubsub to ^0.32.0 (#577)

    7459106

    chore(docs): formatting updates (#577)

    db03a84

    build: do not fail builds on codecov errors (#528) (#577)

    ...

    d60bfd7
19. sofisl

    added a commit that references this issue on Mar 17, 2026

    chore: replace compodoc with jsdoc (#577)

    ...

    b9d724e
20. GautamSharda

    added 2 commits that reference this issue on Mar 23, 2026

    chore: include license in ts declaration file (#577)

    6e6a304

    chore: include license in ts declaration file (#577)

    6991c12
21. shivanee-p

    added a commit that references this issue on Mar 27, 2026

    chore: include license in ts declaration file (#577)

    4810aeb
22. thiyaguk09

    added a commit that references this issue on May 5, 2026

    chore: include license in ts declaration file (googleapis#577)

    25d157e