Skip to content

Release 0.13.0? #382

Description

@ryanseys

We haven't shipped since before Christmas despite numerous changes. I propose we ship 0.13.0 sometime soon. I'd suggest we skip 0.13.0 for superstition but semver might be sad about that.

Activity

  1. stephenplusplus commented on Feb 5, 2015

    @stephenplusplus
    Contributor

    👍

  2. ryanseys commented on Feb 5, 2015

    @ryanseys
    ContributorAuthor

    Will wait for #381 then we can 🚢

  3. ryanseys commented on Feb 9, 2015

    @ryanseys
    ContributorAuthor

    Gonna wait some more for #379 which might introduce breaking changes and this is priority for getting the build working smoothly again.

  4. ryanseys commented on Feb 16, 2015

    @ryanseys
    ContributorAuthor

    How do we release anyway? @silvolu might hold the key.

  5. stephenplusplus commented on Feb 16, 2015

    @stephenplusplus
    Contributor

    We just npm version __major|minor|patch__ and push it to github.

  6. ryanseys commented on Feb 16, 2015

    @ryanseys
    ContributorAuthor

    Oh does @selfiebot see the tag and handle it? It's been so long since a release I forget.

  7. stephenplusplus commented on Feb 16, 2015

    @stephenplusplus
    Contributor

    Yep, @selfiebot is king of npm publish and doc building.

  8. ryanseys commented on Feb 16, 2015

    @ryanseys
    ContributorAuthor

    PRAISE THE KING!

    👑
    @selfiebot

    🙇🙇🙇 <-- gcloud team

  9. ryanseys commented on Feb 17, 2015

    @ryanseys
    ContributorAuthor

    @selfiebot appears to be dead because our docs are not building. Could someone please investigate?

    @jgeewax
    @silvolu

    And teach me how to do it if possible? :)

  10. stephenplusplus commented on Feb 19, 2015

    @stephenplusplus
    Contributor

    I believe we discovered selfie wasn't happy with our failing tests, so it aborted before building the docs. After #402, hopefully the flakiness will be eradicated.

  11. ryanseys commented on Feb 24, 2015

    @ryanseys
    ContributorAuthor

    8eb6pr5

  12. stephenplusplus commented on Mar 5, 2015

    @stephenplusplus
    Contributor

    Not fixed, but too many issues for the same thing :$ Specific issue and discussion for solution: #411

  13. 20 remaining items

  14. added a commit that references this issue on Feb 3, 2026
  15. added a commit that references this issue on Feb 5, 2026
  16. added a commit that references this issue on Feb 23, 2026
  17. added a commit that references this issue on Feb 26, 2026
  18. added a commit that references this issue on Feb 26, 2026
  19. added a commit that references this issue on Mar 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions