Skip to content

Release checklist

Kiran Challa edited this page May 21, 2018 · 19 revisions
  • To stage for a release, bump up the version number in the "version.props" file in the root directory, depending on the type of release (patch vs minor vs major)

  • Run ".\build.cmd" on Powershell to automatically update "package.json" and create a ".nupkg" file.(see README for more info)

  • Copy the generated .nupkg file in a well known 'drops' folder

  • npm RELEASE: Run "npm publish" in the root directory

  • cdnjs RELEASE: cdnjs will pick up the new released version from npmjs in around 12 hours. https://github.com/maruilian11/cdnjs/blob/master/ajax/libs/jquery-validation-unobtrusive/package.json#L24 adds an npm hook that updates the cdnjs after an npm release.

  • NuGet RELEASE: Reach out to @muratg to publish the .nupkg (created in the root directory after running ".\build.cmd") to NuGet

  • Microsoft AJAX CDN RELEASE: Reach out to the owners of Microsoft CDN to host the scripts on it (contact @Eilon for info)

  • Update aspnet/templating with the new version when available on AJAX CDN

  • Update aspnet/identity with the new version when available on AJAX CDN

  • Make sure to create a git tag for the version which was release.

Clone this wiki locally