This is an automated email from the ASF dual-hosted git repository.

asf-gitbox-commits pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/zeppelin-site.git


The following commit(s) were added to refs/heads/asf-staging by this push:
     new 2122dea49 Automatic Site Publish by Buildbot
2122dea49 is described below

commit 2122dea49a45031bf898282b34d23890fc91598b
Author: buildbot <[email protected]>
AuthorDate: Thu Jul 2 09:28:37 2026 +0000

    Automatic Site Publish by Buildbot
---
 output/AGENTS.md    | 86 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 output/atom.xml     |  2 +-
 output/index.html   | 16 +++++-----
 output/rss.xml      |  4 +--
 output/whats_new.md | 16 +++++-----
 5 files changed, 105 insertions(+), 19 deletions(-)

diff --git a/output/AGENTS.md b/output/AGENTS.md
new file mode 100644
index 000000000..8c17f9bdd
--- /dev/null
+++ b/output/AGENTS.md
@@ -0,0 +1,86 @@
+# AGENTS.md
+
+Guidance for coding agents working in this checkout of `apache/zeppelin-site`.
+
+## Repository Shape
+
+- This is the Apache Zeppelin project website, built with Jekyll/GitHub Pages.
+- Root pages, `_includes/`, `_layouts/`, `_plugins/`, `assets/`, 
`download.md`, and `security.md` are live site sources.
+- `docs/<version>/` contains versioned documentation snapshots. Scope edits to 
the exact version or page requested.
+- `output/` and `_site/` are generated or build output. Do not edit them 
unless the user explicitly asks for generated artifacts.
+- `.asf.yaml` declares the ASF website flow: `master` builds to `asf-staging`, 
and `asf-site` is the publish branch.
+
+## Start Every Task
+
+- Run `git status --short --branch` first and preserve unrelated user changes.
+- Start all work from the latest `origin/master`. Fetch it before editing:
+  ```bash
+  git fetch origin master
+  git switch master || git switch --track origin/master
+  git pull --ff-only origin master
+  ```
+- If uncommitted work prevents switching to `master`, stop and ask before 
moving, stashing, or resetting anything.
+- Do not begin content or code edits from `asf-site`, `asf-staging`, or an old 
feature branch.
+- Use `rg` or `rg --files` for searches.
+- In zsh, quote pathspecs that contain globs.
+- Keep changes tightly scoped. Avoid broad formatting changes across 
historical docs.
+
+## Build And Preview
+
+- Build the Docker image and start the dev server:
+  ```bash
+  ./zeppelin-site.sh --build-image
+  ```
+- Start the dev server after the image exists:
+  ```bash
+  ./zeppelin-site.sh
+  ```
+- Preview at `http://localhost:4000`.
+- Build the production site:
+  ```bash
+  ./zeppelin-site.sh --build-dist
+  ```
+- `zeppelin-site.sh` removes `_site/` before serving or building.
+- If dependency troubleshooting is needed, use the repo's Docker path:
+  ```bash
+  docker run --rm -it -v "$(pwd):/app" -w /app zeppelin-site-dev:latest 
/bin/bash -lc "bundle install"
+  ```
+
+## Branch Synchronization Rules
+
+Be extra careful with `asf-site` and `asf-staging`. The user cares about proof 
of which ref moved.
+
+- Do not assume `asf-staging` exists as a local branch. Refresh 
remote-tracking refs directly:
+  ```bash
+  git fetch origin refs/heads/asf-site:refs/remotes/origin/asf-site 
refs/heads/asf-staging:refs/remotes/origin/asf-staging
+  ```
+- Compare before any destructive branch move:
+  ```bash
+  git status --short --branch
+  git remote -v
+  git rev-parse origin/asf-site origin/asf-staging
+  git log --oneline -1 origin/asf-site
+  git log --oneline -1 origin/asf-staging
+  ```
+- If the user asks to make `asf-site` match `asf-staging`, first make sure the 
checked-out branch is `asf-site`, then reset that branch:
+  ```bash
+  git switch asf-site
+  git reset --hard origin/asf-staging
+  ```
+- Force-push only when the user explicitly asks for it:
+  ```bash
+  git push --force origin asf-site
+  ```
+- After pushing, prove the final remote state:
+  ```bash
+  git ls-remote origin refs/heads/asf-site refs/heads/asf-staging
+  ```
+- In the final response, include the exact pushed refspec or push output and 
the final `git ls-remote` result, so it is clear that `asf-site` moved and 
`asf-staging` did not.
+
+## Commit Hygiene
+
+- Preserve ASF license headers.
+- Avoid editing generated search indexes, minified assets, or large historical 
snapshots unless they are the target.
+- For user-facing site edits, run `./zeppelin-site.sh --build-dist` when 
Docker is available and report whether verification passed.
+- PR titles must not have a `codex` prefix. Use a normal project-facing title 
that describes the change.
+- A `codex/` prefix is acceptable for temporary branch names only when the 
user did not request a specific branch name.
diff --git a/output/atom.xml b/output/atom.xml
index 7cd6d174a..7eb45944b 100644
--- a/output/atom.xml
+++ b/output/atom.xml
@@ -4,7 +4,7 @@
  <title>Apache Zeppelin</title>
  <link href="http://zeppelin.apache.org/"; rel="self"/>
  <link href="http://zeppelin.apache.org"/>
- <updated>2026-07-02T00:49:49+00:00</updated>
+ <updated>2026-07-02T09:28:27+00:00</updated>
  <id>http://zeppelin.apache.org</id>
  <author>
    <name>The Apache Software Foundation</name>
diff --git a/output/index.html b/output/index.html
index 46429869a..4c52e6916 100644
--- a/output/index.html
+++ b/output/index.html
@@ -267,31 +267,31 @@ limitations under the License.
 <div class="new">
   <div class="container">
     <h2>What's new in</h2>
-    <span class="newZeppelin center-block">Apache Zeppelin 0.11</span>
+    <span class="newZeppelin center-block">Apache Zeppelin 0.12.1</span>
     <div class="border row">
       <div class="border col-md-4 col-sm-4">
-        <h4>Java 11</h4>
+        <h4>Security Fixes</h4>
         <div>
           <p>
-            Zeppelin 0.11 is built with Java 11. It's recommended to use Java 
11 or later to run Zeppelin.
+            Zeppelin 0.12.1 includes several security fixes, including JWT 
validation, path traversal hardening, and a WebSocket memory leak fix.
           </p>
         </div>
       </div>
 
       <div class="border col-md-4 col-sm-4">
-        <h4>Spark and Flink</h4>
+        <h4>Frontend Upgrades</h4>
         <div>
           <p>
-             The latest version of Apache Spark and Apache Flink are 
supported. You can use the latest features and improvements in Spark and Flink. 
+            Angular 12 and Webpack 5 upgrades improve the web UI foundation, 
with strict template mode enabled.
          </p>
         </div>
       </div>
 
       <div class="border col-md-4 col-sm-4">
-        <h4>Python 3</h4>
+        <h4>Stability Improvements</h4>
         <div>
             <p>
-                Python 3.9 is the default version of Python interpreter. 
+              Spark, Flink, Python, Neo4j, and File interpreters received 
stability improvements, along with CI and E2E testing updates.
             </p>
         </div>
       </div>
@@ -329,7 +329,7 @@ limitations under the License.
 
     <div class="col-md-12 col-sm-12 col-xs-12 text-center">
       <p style="text-align:center; margin-top: 32px; font-size: 14px; color: 
gray; font-weight: 200; font-style: italic; padding-bottom: 0;">See more 
details in 
-        <a href="./releases/zeppelin-release-0.11.2.html">0.11.2 Release 
Note</a>
+        <a href="./releases/zeppelin-release-0.12.1.html">0.12.1 Release 
Note</a>
       </p>
     </div>
 
diff --git a/output/rss.xml b/output/rss.xml
index e2583bd30..62aff76f3 100644
--- a/output/rss.xml
+++ b/output/rss.xml
@@ -5,8 +5,8 @@
         <description>Apache Zeppelin - The Apache Software 
Foundation</description>
         <link>http://zeppelin.apache.org</link>
         <link>http://zeppelin.apache.org</link>
-        <lastBuildDate>2026-07-02T00:49:49+00:00</lastBuildDate>
-        <pubDate>2026-07-02T00:49:49+00:00</pubDate>
+        <lastBuildDate>2026-07-02T09:28:27+00:00</lastBuildDate>
+        <pubDate>2026-07-02T09:28:27+00:00</pubDate>
         <ttl>1800</ttl>
 
 
diff --git a/output/whats_new.md b/output/whats_new.md
index 28f83eb55..d7ddf8bec 100644
--- a/output/whats_new.md
+++ b/output/whats_new.md
@@ -16,31 +16,31 @@ limitations under the License.
 <div class="new">
   <div class="container">
     <h2>What's new in</h2>
-    <span class="newZeppelin center-block">Apache Zeppelin 0.11</span>
+    <span class="newZeppelin center-block">Apache Zeppelin 0.12.1</span>
     <div class="border row">
       <div class="border col-md-4 col-sm-4">
-        <h4>Java 11</h4>
+        <h4>Security Fixes</h4>
         <div>
           <p>
-            Zeppelin 0.11 is built with Java 11. It's recommended to use Java 
11 or later to run Zeppelin.
+            Zeppelin 0.12.1 includes several security fixes, including JWT 
validation, path traversal hardening, and a WebSocket memory leak fix.
           </p>
         </div>
       </div>
 
       <div class="border col-md-4 col-sm-4">
-        <h4>Spark and Flink</h4>
+        <h4>Frontend Upgrades</h4>
         <div>
           <p>
-             The latest version of Apache Spark and Apache Flink are 
supported. You can use the latest features and improvements in Spark and Flink. 
+            Angular 12 and Webpack 5 upgrades improve the web UI foundation, 
with strict template mode enabled.
          </p>
         </div>
       </div>
 
       <div class="border col-md-4 col-sm-4">
-        <h4>Python 3</h4>
+        <h4>Stability Improvements</h4>
         <div>
             <p>
-                Python 3.9 is the default version of Python interpreter. 
+              Spark, Flink, Python, Neo4j, and File interpreters received 
stability improvements, along with CI and E2E testing updates.
             </p>
         </div>
       </div>
@@ -78,7 +78,7 @@ limitations under the License.
 
     <div class="col-md-12 col-sm-12 col-xs-12 text-center">
       <p style="text-align:center; margin-top: 32px; font-size: 14px; color: 
gray; font-weight: 200; font-style: italic; padding-bottom: 0;">See more 
details in 
-        <a href="./releases/zeppelin-release-0.11.2.html">0.11.2 Release 
Note</a>
+        <a href="./releases/zeppelin-release-0.12.1.html">0.12.1 Release 
Note</a>
       </p>
     </div>
 

Reply via email to