You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Lewis John McGibbney (Jira)" <ji...@apache.org> on 2026/02/18 01:06:00 UTC

[jira] [Resolved] (TIKA-4661) Automate tika-helm release on Tika version update

     [ https://issues.apache.org/jira/browse/TIKA-4661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lewis John McGibbney resolved TIKA-4661.
----------------------------------------
    Resolution: Fixed

> Automate tika-helm release on Tika version update
> -------------------------------------------------
>
>                 Key: TIKA-4661
>                 URL: https://issues.apache.org/jira/browse/TIKA-4661
>             Project: Tika
>          Issue Type: Improvement
>          Components: tika-helm
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Major
>             Fix For: 3.3.0
>
>
> I want to automate the tika-helm release process that is currently performed manually after merging automated version-bump PRs. GitHub Actions workflows must handle tagging, GitHub Release creation, and publishing the Helm chart to Apache JFrog Artifactory. This will essentially replace the manual release management workflow documented at [https://cwiki.apache.org/confluence/display/TIKA/Release+Process+for+tika-helm]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)