Skip to content

Release checklist

Jump to bottom
Artak edited this page Jul 26, 2022 · 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 here.

  • 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 @mkArtakMSFT to publish the .nupkg (created in the artifacts\build directory after running ".\build.cmd") to NuGet. For now we'll have to get @joeloff to sign these packages first, but we'll eventually need to create a better workflow.

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

  • Let @ChrisSfanos know about a new version so that he publishes the update to https://ajax.aspnetcdn.com.

  • Verify that the documentation for these new urls are updated here https://docs.microsoft.com/en-us/aspnet/ajax/cdn/overview#aspnet-mvc-releases-on-the-cdn

  • 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