Skip to content

Make periodic pre-release builds available on npm #1882

Closed

Description

We should be making preview releases on npm available, preferably in an automated fashion.

As discussed a bit on #1818.

Seems like this should have the 1.5 milestone (but should begin prior to 1.5's release, as would be appropriate).

Activity

  1. RyanCavanaugh commented on Feb 2, 2015

    @RyanCavanaugh
    Member

    I believe the only outstanding question we had here was how to do this in a way that people who didn't specify a version number in their package.json didn't automatically upgrade to some possibly-unstable TypeScript build.

  2. Arnavion commented on Feb 2, 2015

    @Arnavion

    Assuming you'll use prerelease tags (eg 1.5.0-prerelease.2015.02.02.abcd) npm will never choose this to install unless the requested version also contains a prerelease tag. See https://github.com/npm/node-semver#prerelease-tags for details.

    Prerelease tags are also considered less than their corresponding release, so the above would be less than 1.5.0 when it's actually released. From the semver spec:

    1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0

    Can you detail what version format you're going to use for the prereleases?

  3. danielearwicker commented on Mar 13, 2015

    @danielearwicker

    👍 very keen to have this!

  4. added
    Needs ProposalThis issue needs a plan that clarifies the finer details of how it could be implemented.
    and removed on May 19, 2015
  5. RyanCavanaugh commented on May 19, 2015

    @RyanCavanaugh
    Member

    Let's figure out what the right way to do this is.

  6. DanielRosenwasser commented on Jun 18, 2015

    @DanielRosenwasser
    MemberAuthor

    This appears to be a duplicate of #964.

  7. locked and limited conversation to collaborators on Jun 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    DuplicateAn existing issue was already createdNeeds ProposalThis issue needs a plan that clarifies the finer details of how it could be implemented.SuggestionAn idea for TypeScript

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions