New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@davidspekorg/semantic-release-helm

Package Overview
Dependencies
Maintainers
1
Versions
3
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@davidspekorg/semantic-release-helm

Helm plugin for [semantic-release](https://github.com/semantic-release/semantic-release)

  • 1.1.1
  • latest
  • Source
  • npm
  • Socket score

Version published
Maintainers
1
Created
Source

semantic-release-helm

semantic-release plugin to publish a helm chart to a helm repository and an OCI registry.

It updates Helm chart version and appVersion in Chart.yaml.

It supports the following protocols:

Install

npm install -D @davidspekorg/semantic-release-helm

Configuration

OptionsDescriptionsRequiredtypeDefault
chartRepositoryURI for chart repositoryyes*stringnone
ociRegistryURI for OCI registryyes*stringnone
chartDirectoryChart directory where Chart.yml is locatednostring.
versionUpdatePolicySet update policy for version field of Chart.yamlno"fixed" | "sync" | "desync""sync"
appVersionUpdatePolicySet update policy for appVersion field of Chart.yamlno"fixed" | "sync" | "desync""sync"

* At least one of ociRegistry or chartRepository is required.

Pass credentials through environment variable to login helm repository.

export HELM_REPOSITORY_USERNAME=<USERNAME>
export HELM_REPOSITORY_PASSWORD=<PASSWORD>
export HELM_REGISTRY_USERNAME=<USERNAME>
export HELM_REGISTRY_PASSWORD=<PASSWORD>

HELM_REPOSITORY_USERNAME and HELM_REPOSITORY_PASSWORD are used for chart repository login.

HELM_REGISTRY_USERNAME and HELM_REGISTRY_PASSWORD are used for OCI registry login.

If you are using oci registry and no credentials are provided, it will use the HELM_REPOSITORY_USERNAME and HELM_REPOSITORY_PASSWORD for login.

About versionUpdatePolicy & appVersionUpdatePolicy

Update policy

  • fixed: Use Fixed version. The version will not be updated
  • sync: Use nextRelease.version. New version will be set to nextRelease.version
  • desync: Version will be increased according to nextRelease.type (one of major, premajor, minor, preminor, patch, prepatch, prerelease)

Example

{
  "plugins": [
    [
      "@davidspekorg/semantic-release-helm",
      {
        "chartRepository": "https://mychart.company.org/chartrepo/myproject",
        "ociRegistry": "mychart.company.org/myproject",
        "chartDirectory": "./chart",
        "versionUpdatePolicy": "sync",
        "appVersionUpdatePolicy": "fixed"
      }
    ]
  ]
}
  • Your chart repository is https://mychart.company.org/chartrepo/myproject and OCI registry is mychart.company.org/myproject.
  • Chart.yaml is in chart sub-directory
  • version will follow next release version and appVersion will not modified

Old version

# semantic-release version: 1.2.3
version: 1.2.3
appVersion: 2.3.1

New version - Case #1 patch

# semantic-release version: 1.2.4
version: 1.2.4
appVersion: 2.3.1

New version - Case #2 minor

# semantic-release version: 1.3.0
version: 1.3.0
appVersion: 2.3.1

New version - Case #3 major

# semantic-release version: 2.0.0
version: 2.0.0
appVersion: 2.3.1

FAQs

Package last updated on 25 Nov 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc