Mercurial > repos > other > Puppet
view modules/stdlib/RELEASE_PROCESS.markdown @ 476:b0531370e183 default tip
Avoid fully controllable rewrite prefix
Apache doesn't guarantee that rewrites are URLs or paths
within the prefix and will process them rather than error,
so close a fully controllable rewrite prefix:
https://blog.orange.tw/2024/08/confusion-attacks-en.html?m=1
author | IBBoard <dev@ibboard.co.uk> |
---|---|
date | Sun, 11 Aug 2024 13:29:59 +0100 |
parents | 4a2ee7e3b110 |
children |
line wrap: on
line source
# Contributing to this module # * Work in a topic branch * Submit a github pull request * Address any comments / feeback * Merge into main using --no-ff # Releasing this module # * This module adheres to http://semver.org/ * Look for API breaking changes using git diff vX.Y.Z.. * If no API breaking changes, the minor version may be bumped. * If there are API breaking changes, the major version must be bumped. * If there are only small minor changes, the patch version may be bumped. * Update the CHANGELOG * Update the Modulefile * Commit these changes with a message along the lines of "Update CHANGELOG and Modulefile for release" * Create an annotated tag with git tag -a vX.Y.Z -m 'version X.Y.Z' (NOTE the leading v as per semver.org) * Push the tag with git push origin --tags * Build a new package with puppet-module or the rake build task if it exists * Publish the new package to the forge * Bonus points for an announcement to puppet-users.