Cwikius-Spring/spring-security
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-security.git synced 2025-07-07 11:12:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add steps for dependency locks

Rob Winch 2020-01-07 21:34:01 -06:00
parent 4b9a508415
commit 77e1a1f6bb
1 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Release-Process.md

@ -23,6 +23,10 @@
#### 1. Update dependencies #### 1. Update dependencies
If you are on master use 1.b, otherwise use 1.a
#### 1.a Updating Manually
- Dependencies are declared in `gradle/dependency-management.gradle` - Dependencies are declared in `gradle/dependency-management.gradle`
- Update Spring Framework and Spring Data at a minimum - Update Spring Framework and Spring Data at a minimum
- Then find dependencies that need updating by running the `update-dependencies.sh` script: - Then find dependencies that need updating by running the `update-dependencies.sh` script:
@ -31,6 +35,18 @@
``` ```
_Prerequisites: The `build` directory has to exist to store the file `build/updates.txt`. This directory gets created when a new build is run, but is not present on a fresh git clone._ _Prerequisites: The `build` directory has to exist to store the file `build/updates.txt`. This directory gets created when a new build is run, but is not present on a fresh git clone._
#### 1.b Lock Dependencies
Master is setup to use Gradle [dependency locking](https://docs.gradle.org/current/userguide/dependency_locking.html) and version ranges so builds automatically take advantage of the latest dependencies. In order to ensure releases are reproducible, we must lock the dependencies before a release.
To lock the dependencies execute:
```
./gradlew writeLocks --write-locks
```
This writes out all the resolved versions. Run the build. If it passes, commit the changes.
#### 2. Update release version #### 2. Update release version
- Update the version number in `gradle.properties` for the release, for example, `5.1.0.M1`, `5.1.0.RC1`, `5.1.0.RELEASE` - Update the version number in `gradle.properties` for the release, for example, `5.1.0.M1`, `5.1.0.RC1`, `5.1.0.RELEASE`
@ -68,6 +84,7 @@ git push origin 5.2.0.RC1
#### 7. Update to next development version #### 7. Update to next development version
- Update release version to next `BUILD-SNAPSHOT` version and then push - Update release version to next `BUILD-SNAPSHOT` version and then push
- If dependency locks (1.b) were used, revert the commit that included the lock files so that the build uses the latest versions again.
#### 8. Update version on project page #### 8. Update version on project page