| commit | c07c004955cd680ae4e0c57b2857c2fe0fe5f128 | [log] [tgz] |
|---|---|---|
| author | Andor Molnar <andor@cloudera.com> | Thu Mar 14 11:07:26 2024 -0500 |
| committer | Andor Molnar <andor@cloudera.com> | Thu Mar 14 11:07:26 2024 -0500 |
| tree | cd33d522e82f2af211ee9d4836a8becd4c62bc8d | |
| parent | e6254851dfed71b7b87e68b6098551f918bce919 [diff] |
CVE-2024-23944
This branch houses the production Apache ZooKeeper website.
Updating this branch and pushing to the Apache git repo will cause gitpubsub to publish the site - BE CAREFULL!
Typically the website will need to be updated as part of a release. Prior to updating this branch update the “website” branch appropriately, “jekyl build”, update the product docs, APIs, etc... and then reviewed the staged site as detailed in the website branch README.
After verifying the staged site you can:
git checkout asf-site - checkout this branchrm -fr content - remove the old site contentmv _site content - rename the staged site directory. You should still have this from the prior staging effortsgit add . - update git appropriately (may include git rm, etc..., as well).git commit - ensure an good commit messagegit push <origin> asf-site - point of no return.At this point you can verify that the production site is updated and the links, etc... are functioning properly.