Skip to content

docs(answer): document 2.0.2 notification controls - #458

Merged
mberlofa merged 1 commit into
mainfrom
docs/answer-2.0.2
Jul 30, 2026
Merged

docs(answer): document 2.0.2 notification controls#458
mberlofa merged 1 commit into
mainfrom
docs/answer-2.0.2

Conversation

@mberlofa

@mberlofa mberlofa commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Summary

  • updates the Apache Answer image reference to 2.0.2
  • documents the new typed settings for the new-question email worker
  • keeps the complete values reference aligned with the chart defaults and schema

User impact

Users can see the supported queue-size and send-interval controls introduced with Answer 2.0.2 directly in the chart documentation.

Validation

  • npm run lint
  • npm run format:check
  • npm run build (162 pages generated; 158 indexed by Pagefind)
  • make site-sync-check CHART=answer
  • make release-check REPO=site
  • make attribution-check REPO=site

Self-review

  • reviewed the complete diff against main
  • confirmed only the Answer chart page changed
  • confirmed documented defaults and bounds match the chart values and upstream behavior
  • confirmed no stale Answer image version remains in the changed reference

Companion chart PR: helmforgedev/charts#860.

Related to helmforgedev/charts#831.

Summary by CodeRabbit

  • Documentation
    • Updated the Apache Answer Helm chart documentation to reference container image tag 2.0.2.
    • Added documentation for notification queue size and email send interval settings.
    • Retained existing configuration references for site details, language, contact email, installation, logging, and environment variables.

@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The Apache Answer Helm chart documentation updates the default container image tag from 2.0.0 to 2.0.2 and documents queue size and send interval settings for new-question email notifications.

Changes

Answer chart documentation

Layer / File(s) Summary
Update chart configuration reference
src/pages/docs/charts/answer.mdx
The documented default image tag is updated to 2.0.2, and queueSize and sendIntervalSeconds notification parameters are added.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related issues

  • helmforgedev/charts#831 — The image tag update to 2.0.2 directly matches the issue’s upstream image update.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title is concise and accurately summarizes the docs update for Answer 2.0.2 notification controls.
Description check ✅ Passed The description covers summary, validation, and related issue, but it does not follow the template's Quality Gates checklist format.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/answer-2.0.2

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/pages/docs/charts/answer.mdx`:
- Around line 249-250: Update the documentation for
answer.notifications.newQuestionEmail.queueSize and sendIntervalSeconds to use
the supported answer.extraEnv configuration, showing the corresponding
NEW_QUESTION_NOTIFICATION_EMAIL_QUEUE_SIZE and
NEW_QUESTION_NOTIFICATION_EMAIL_SEND_INTERVAL_SECONDS environment variables;
remove the nested option rows if they cannot be documented accurately.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: da26405a-4191-480c-bbc9-4c82c3c52717

📥 Commits

Reviewing files that changed from the base of the PR and between 308ee1a and 4a7be26.

📒 Files selected for processing (1)
  • src/pages/docs/charts/answer.mdx

Comment thread src/pages/docs/charts/answer.mdx
@mberlofa
mberlofa merged commit c3d5bde into main Jul 30, 2026
6 checks passed
@mberlofa
mberlofa deleted the docs/answer-2.0.2 branch July 30, 2026 01:26
mberlofa added a commit to helmforgedev/charts that referenced this pull request Jul 30, 2026
## Summary

- upgrades the official Apache Answer image from `2.0.1` to `2.0.2`
- exposes the new-question email queue size and send interval as typed
chart values
- validates the new values with unit, schema, template, and behavioral
k3d scenarios
- updates the chart README and synchronizes the site documentation in
helmforgedev/site#458

Closes #831.

## Upstream review

- release: https://github.com/apache/answer/releases/tag/v2.0.2
- comparison: apache/answer@v2.0.1...v2.0.2
- image: `docker.io/apache/answer:2.0.2`, verified for `linux/amd64` and
`linux/arm64`

Answer 2.0.2 adds reasoning content in AI chat, optional email
verification, recovery middleware, configurable new-question email
delivery, and several authorization and account-hardening fixes. The
release does not change the chart's port, storage path, or database
contract.

## User impact

The upgrade is backward compatible with the existing defaults. Operators
may now configure:

- `answer.notifications.newQuestionEmail.queueSize` (`1` to `65536`,
default `1024`)
- `answer.notifications.newQuestionEmail.sendIntervalSeconds` (`0` to
`300`, default `0`)

## Validation

- `make image-verify IMAGE=docker.io/apache/answer:2.0.2`
- `make deps-check CHART=answer`
- `make validate-chart CHART=answer`
  - 19 layers passed
  - 10 behavioral k3d scenarios passed
  - all workloads Ready, zero restarts, clean crash/fatal log scan
- default, backup, external database, External Secrets, Gateway API,
Ingress, MySQL, PostgreSQL, and new email-worker scenarios covered
- schema rejection verified for queue size `0` and interval `301`
- `make standards-check CHART=answer`
- `node scripts/charts/template-standards-check.js --chart answer`
- `make site-sync-check CHART=answer`
- `make release-check REPO=charts`
- `make attribution-check REPO=charts`
- `make preflight`

## Self-review

- reviewed every changed line against `main`
- confirmed the image and `appVersion` match the latest stable upstream
release
- confirmed no chart package version was edited
- confirmed the new schema bounds match the upstream constants
- confirmed the new values render the exact upstream environment
variables
- confirmed no stale `2.0.1` reference remains under `charts/answer`
- confirmed the diff contains no unrelated changes or attribution
trailers


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **New Features**
* Added configuration for new-question email delivery, including queue
capacity and sending intervals.
* Added support for disabling email throttling by setting the interval
to zero.
* Exposed the new settings through Helm chart values and deployment
configuration.

* **Documentation**
  * Updated chart documentation with the new notification settings.

* **Chores**
  * Updated the application image and chart version to 2.0.2.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: MergeCheck <mergecheck@example.invalid>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant