Skip to content

Release checklist

Jump to bottom
Kiran Challa edited this page May 22, 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 (see README for more info). You should see the output generated under artifacts\build folder.

  • npm RELEASE: Follow the instructions for publishing to NPM registry in internal OneNote.

  • 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 Artak to publish the .nupkg (created in the artifacts\build 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)

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

  • Verify the files are available on AJAX CDN

    - https://ajax.aspnetcdn.com/ajax/jquery.validation.unobtrusive/[version-here]/jquery.validate.unobtrusive.js
- https://ajax.aspnetcdn.com/ajax/jquery.validation.unobtrusive/[version-here]/jquery.validate.unobtrusive.min.js

  • Update aspnet/templating with the new version when available on AJAX CDN and also update the fallback source folders accordingly.

  • Update aspnet/identity with the new version when available on AJAX CDN and also update the fallback source folders accordingly.

  • Update aspnet/scaffolding with the new version when available on AJAX CDN and also update the fallback source folders accordingly.

Clone this wiki locally