Contributions: Release

Release

Major x.0.0

• make sure all deprecations to be removed in x.0.0 are removed
• check that schematics work
• checkout and build the latest N-1.X.X demo site version, remove versions.json from it and add <meta name="robots" content="noindex"> to the index.html
• check in the built N-1.X.X demo versions in demo/src/public/releases/N-1.x folder and update versions.json

Minor x.x.0

• go through feat commits and update new feature comments with @since x.x.0 and deprecated ones with @deprecated x.x.0 Explanation why here
• for each new API field check if static ngAcceptInputType_XXX: XXX; needs to be added
• commit documentation changes

Patch X.X.X + publish

• make sure you're on the master branch and you're ready to release
• generate the new release (yarn version). This will generate a tagged release commit with changelog updates, build the library and the demo site.
• check the CHANGELOG.md in the last commit. If necessary update the file and run yarn changelog:patch to amend changelog and update the git release tag.
• push to npm (cd dist/ng-bootstrap, npm publish, cd ../..). There is no way of NOT rewriting the latest tag in npm, so when publishing OLDER releases, you have to manually restore the latest tag with npm dist-tags add @ng-bootstrap/ng-bootstrap@Z.Z.Z latest
• push master to GitHub (git push upstream)
• push tags to GitHub (git push upstream --tags)
• push the demo site (yarn demo:publish)
• close the release milestone
• create a GitHub release based on the latest tag and copy/paste changelog (to be automated...)
• let the World know!