![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@davidspekorg/semantic-release-helm
Advanced tools
Helm plugin for [semantic-release](https://github.com/semantic-release/semantic-release)
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:
npm install -D @davidspekorg/semantic-release-helm
Options | Descriptions | Required | type | Default |
---|---|---|---|---|
chartRepository | URI for chart repository | yes* | string | none |
ociRegistry | URI for OCI registry | yes* | string | none |
chartDirectory | Chart directory where Chart.yml is located | no | string | . |
versionUpdatePolicy | Set update policy for version field of Chart.yaml | no | "fixed" | "sync" | "desync" | "sync" |
appVersionUpdatePolicy | Set update policy for appVersion field of Chart.yaml | no | "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.
Update policy
nextRelease.version
. New version will be set to nextRelease.version
nextRelease.type
(one of major
, premajor
, minor
, preminor
, patch
, prepatch
, prerelease
){
"plugins": [
[
"@davidspekorg/semantic-release-helm",
{
"chartRepository": "https://mychart.company.org/chartrepo/myproject",
"ociRegistry": "mychart.company.org/myproject",
"chartDirectory": "./chart",
"versionUpdatePolicy": "sync",
"appVersionUpdatePolicy": "fixed"
}
]
]
}
https://mychart.company.org/chartrepo/myproject
and OCI registry is mychart.company.org/myproject
.Chart.yaml
is in chart
sub-directoryversion
will follow next release version and appVersion
will not modifiedOld 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
Helm plugin for [semantic-release](https://github.com/semantic-release/semantic-release)
We found that @davidspekorg/semantic-release-helm demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
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.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.