[RELEASE] Release version 3.3.1

[github-actions]

Release OpenSearch 3.3.1

I noticed that a manifest was automatically created in manifests/3.3.1. Please follow the following checklist to make a release.

---

This release is opened due to a bug in the original 3.3.0 release, only OS updated to 3.3.1 version here.

• [BUG] Upgrade from 2.19.2 to 3.3.0 failed OpenSearch#19660
• [BUG] illegal_argument_exception error after upgrading to 3.3.0 OpenSearch#19646

Related PRs:

• Fix CHANGELOG on 3.3 release branch OpenSearch#19598
• Revert "Enable skip_list for @timestamp field or index sort field  OpenSearch#19661
• [Backport 3.3] Fix issue with updating core with a patch number other than 0 OpenSearch#19667
• [AUTO] Increment version to 3.3.1. OpenSearch#19662
• [Backport 3.3] Onboarding new maven snapshots publishing to s3 (OpenSearch Core) OpenSearch#19668
• [Backport 3.3] [Bug Fix] [Star Tree] Fix sub-aggregator casting for search with profile=true OpenSearch#19669
• Fix @timestamp upgrade issue by adding a version check on skip_list param (3.3) OpenSearch#19671
• [AUTO] Add release notes for 3.3.1 OpenSearch#19679
• [AUTO] Update input manifests #5783
• [3.3.0] Manifest Commit Lock with action UPDATE_TO_RECENT_COMMITS #5786
• Add 3.3.1 version history and OS bump only, OSD remains 3.3.0 documentation-website#11345
  • Update dashboards installation to use site.opensearch_dashboards_version documentation-website#11399
• [Enhancement] Relax integTest OSD version matching to only major.minor #5787
  • Relax integTest OSD to match only Major.Minor versions before triggering #5788
• Bump OS 3.3.1 ansible-playbook#195
• Bump OS 3.3.1 helm-charts#705
• Add the 3.3.1 consolidated release notes #5791
• Support central release of either opensearch or opensearch-dashboards or both #5793
  • Resolve step issues in jenkins workflow #5796
  • Update PRODUCTS to PROJECTS to be consistent with var name #5797

Release Schedule:

• 2025/10/17: OpenSearch Core issues resolve by EOD Friday
• 2025/10/17: First RC build by late Friday and run integTest of all OS 3.3.1 + OSD 3.3.0
• 2025/10/20: Evaluate with Core owner & sanity test
• 2025/10/21: Quick release 3.3.1 launch on Tuesday
• 2025/10/22: Quick release 3.3.1 launch on Wednesday due to a small bug

Potential 3.3.2 2025/10/30 (Pending Backport 3.3) ⚠️

• opensearch-build:
  • Added dependent plugins for search relevance #5794
  • [AUTO] Update input manifests #5798
• OpenSearch:
  • Similar to [AUTO] Increment version to 3.3.1. OpenSearch#19662 in branch 3.3
    • Bump 3.3 branch to version 3.3.2 OpenSearch#19732
  • Similar to Fix bwc on main by adding 3.3.1 to bwcVersions OpenSearch#19703 in branch main
    • Bump bwc on main with 3.3.2 bwcVersions OpenSearch#19734
  • [Backport 3.3] Remaining Lucene103Codec changes OpenSearch#19739
• Docs:
  • Bump docs to 3.3.2 version with OS updates only documentation-website#11404
• Potential Neural Search
  • [Agentic Search] Update User Prompt with output format instructions neural-search#1621
    • [Backport 3.3] [Agentic Search] Update User Prompt with output format instructions neural-search#1623
  • [Agentic Search] Add conversation search support with agentic search neural-search#1626
    • [Backport 3.3] [Agentic Search] Add conversation search support with agentic search neural-search#1627
  • [Java Agent] Allow JRT protocol URLs in protection domain extraction OpenSearch#19683
    • [Backport 3.3] [Java Agent] Allow JRT protocol URLs in protection domain extraction OpenSearch#19709
• Potential ML/MCP:
  • [Java Agent] Allow JRT protocol URLs in protection domain extraction OpenSearch#19683
  • [BUG] Failed to get tools from external MCP server ml-commons#4209
    • [Backport 3.3] add refresh policy; add checkpoint id field ml-commons#4306
    • combine json chunks from requests ml-commons#4317
    • Fix unsupported operation exception in execute tool API ml-commons#4325
    • [Backport 3.3] Onboard to s3 snapshots ml-commons#4328
• Potential k-NN:
  • [Backport 3.3] Do not apply memory optimized search for old indices. k-NN#2949
• Potential skills:
  • Fixing regex bypass issue ml-commons#4336
  • fix regex bypass issue skills#656

---

How to use this issue

This Release Issue

This issue captures the state of the OpenSearch release, its assignee (Release Manager) is responsible for driving the release. Please contact them or @mention them on this issue for help. There are linked issues on components of the release where individual components can be tracked. For more information check the the Release Process OpenSearch Guide.

Please refer to the following link for the release version dates: Release Schedule and Maintenance Policy.

Release Checklist

Entrance Criteria

Criteria	Status	Description	Comments
Each component release issue has an assigned owner	🔴
Documentation draft PRs are up and in tech review for all component changes	🔴
Sanity testing is done for all components	🔴
Code coverage has not decreased (all new code has tests)	🔴
Release notes are ready and available for all components	🔴
Roadmap is up-to-date (information is available to create release highlights)	🔴
Release ticket is cut, and there's a forum post announcing the start of the window	🔴
Any necessary security reviews are complete	🔴

OpenSearch 3.3.1 exit criteria status:

Criteria	Status	Description	Comments
Performance tests are run, results are posted to the release ticket and there no unexpected regressions	🔴
No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days	🔴
Documentation has been fully reviewed and signed off by the documentation community.	🔴
All integration tests are passing	🔴
Release blog is ready	🔴

OpenSearch-Dashboards 3.3.1 exit criteria status:

Criteria	Status	Description	Comments
Documentation has been fully reviewed and signed off by the documentation community	🔴
No unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days	🔴
All integration tests are passing	🔴
Release blog is ready	🔴

Preparation

• Release manager assigned.
• Update release page on the website with release manager and release issue details. Sample PR
• Existence of label in each component repo. For more information check the release-label section.
• Increase the build frequency.
• Release Issue.

Campaigns

• Component Release Issue.
• Release Campaigns.

Version Increment - _Ends REPLACE_RELEASE-minus-10-days

• Core Version Increment.
• Components Version Increment.

Feature Freeze - _Ends REPLACE_RELEASE-minus-12-days

• OpenSearch / OpenSearch-Dashboards core and components teams finalize their features.

Code Complete - Ends REPLACE_RELEASE-minus-10-days

• Mark this as done once the Code Complete is reviewed.
• Create/Verify pull requests to add each component to relase input manifests/3.3.1/opensearch-3.3.1.yml and manifests/3.3.1/opensearch-dashboards-3.3.1.yml.

Release Branch, Release Candidate Creation and Testing - Ends REPLACE_RELEASE-minus-6-days

• Core Release Branch.
• Components Release Branch.
• Generate Release Candidate.
• Docker Scan.
• Integ Test.
  • TAR
  • RPM
  • DEB
  • Windows
• Backwards Compatibility Tests.
• Broadcast and Communication.
• Release Candidate Lock.
• Stop Release Candidate periodic auto builds

Performance testing validation - Ends REPLACE_RELEASE-minus-6-days

• Post the benchmark-tests
• Longevity tests do not show any issues.

Pre Release - Ends REPLACE_RELEASE-minus-1-days

• Release Labeled Issues.
• Go or No-Go.
• Release Notes.

Release - _Ends {_REPLACE_RELEASE-day}

• Central Promotion Workflow.
• Collaboration with the Project Management Team.

Release Checklist.

Pre-Release activities

• Promote Repos.
  • • OS
  • • OSD
• Promote Artifacts.
  • • Windows
  • • Linux Debian
  • • Linux RPM
  • • Linux TAR
• Consolidated Release Notes.

Release activities

• Docker Promotion.
• Release Validation part 1.
  • • OpenSearch and OpenSearch Dashboard Validation.
  • • Validate the native plugin installation.
• Merge consolidated release notes PR.
• Website and Documentation Changes.
  • • Merge staging website PR.
  • • Promote the website changes to prod.
  • • Add website alert.
• Release Validation part 2.
  • • Validate the artifact download URL's and signatures.
• Release Validation part 3.
  • • Trigger the validation build (Search for Completed validation for <> in the logs).
• Maven Promotion.
• Publish blog posts.
• Advertise on Social Media.
• Post on public slack and Github Release issue.

Post Release

• Release Tags.
• Input Manifest Update.
• OpenSearch Build Release notes.
• Decrease the Build Frequency.
• Retrospective Issue.
• Helm and Ansible Playbook release.
• Upcoming Release Preparation.

Components

Replace with links to all component tracking issues.

Component	On track	Release Notes
{COMPONENT_ISSUE_LINK}	{INDICATOR}	{STATUS}

Legend

Symbol	Meaning
🟢	On track with overall release
🟡	Missed last milestone
🔴	Missed multiple milestones