You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@allura.apache.org by br...@apache.org on 2026/08/31 15:06:52 UTC
(allura) branch master updated: CHANGES updated for ASF release 1.21.0
This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/allura.git
The following commit(s) were added to refs/heads/master by this push:
new 467bdd4ed CHANGES updated for ASF release 1.21.0
467bdd4ed is described below
commit 467bdd4ede27ebddf001504b49492fe377845315
Author: Dave Brondsema <da...@brondsema.net>
AuthorDate: Mon Aug 31 09:57:47 2026 -0400
CHANGES updated for ASF release 1.21.0
---
CHANGES | 38 ++++++++++++++++++++++++++------------
1 file changed, 26 insertions(+), 12 deletions(-)
diff --git a/CHANGES b/CHANGES
index aa6016b91..4e3e384b6 100644
--- a/CHANGES
+++ b/CHANGES
@@ -1,21 +1,35 @@
-Version 1.20.1 (Unreleased)
+Version 1.21.0 (September 2026)
Upgrade Instructions
- New feature, ENABLED BY DEFAULT: repo admins can turn force push on and off for their own git
- repos, from the repo's admin page. Allura writes `receive.denyNonFastForwards` in each repo's
- own config, and now writes it for every repo it creates or clones.
- To keep the previous behaviour, set `scm.force_push.git.enabled = false` in your .ini file
- before upgrading. With it off, Allura touches no repo's config and shows no admin UI.
+ Stop any running Allura services while upgrading.
- Record what each existing repo already permits, so the admin page shows the right value.
- Run in the Allura dir (replace your .ini file path):
- `paster script your-ini-file.ini ../scripts/migrations/force-push-sync-from-repo-config.py -- --dry-run`
- Check the output, then run it again without `--dry-run` to apply. The script reads each git
- repo and writes only to Mongo. It changes no repository.
+ Install updated dependencies by running:
+ pip install -r requirements.txt --no-deps --upgrade --upgrade-strategy=only-if-needed
+
+ To allow repo admins to turn force push on and off for their own git repos, add
+ `scm.force_push.git.enabled = true` to your .ini file and run in the Allura dir (replace your .ini file path):
+ `paster script your-ini-file.ini ../scripts/migrations/force-push-sync-from-repo-config.py`
+ The script reads each git repo's settings and records it in Mongo so the admin page shows the right value.
+ It does not change any repository.
New Features
- * [#686] Repo admins can allow force push on their own git repos, without a support request
+ * [#686] Repo admins can allow force push on their own git repos
+ * Add mongodb option for the jinja bytecode cache
+
+Security Improvements
+ * bumping webob 1.8.10 -> 1.8.11
+ * strengthen _verify_return_to and tests for webob upgrade
+ * start a SECURITY.md
+ * Prevent re-tracking revoked sessions
+
+Code Repos
+ * [#8620] Fix git rename handling
+
+For Developers
+ * update discussion thread logic for consistency
+ * increase ulimits on docker web to avoid "Too many open files" during test runs at least
+
Version 1.20.0 (August 2026)