v0.10.0

chore(deps): update golang docker tag to v1.22.2 @renovate (#23)

This PR contains the following updates:

Package	Type	Update	Change
golang	stage	minor	1.20.3-bullseye -> 1.22.2-bullseye

---

Fix Docker promote @goruha (#25)

## what * Fix Docker promote

v0.9.0

chore(deps): update alpine docker tag to v3.19 @renovate (#22)

This PR contains the following updates:

Package	Type	Update	Change
alpine	final	minor	3.17 -> 3.19

---

Configure Renovate @renovate (#9)

Welcome to [Renovate](https://togithub.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• Dockerfile (dockerfile)
• .github/workflows/docker-promote.yml (github-actions)
• .github/workflows/feature-branch.yml (github-actions)
• .github/workflows/release.yml (github-actions)
• go.mod (gomod)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

With your current configuration, Renovate will create 2 Pull Requests:

chore(deps): update alpine docker tag to v3.19

• Schedule: ["at any time"]
• Branch name: renovate/alpine-3.x
• Merge into: master
• Upgrade alpine to 3.19

chore(deps): update golang docker tag to v1.22.2

• Schedule: ["at any time"]
• Branch name: renovate/golang-1.x
• Merge into: master
• Upgrade golang to 1.22.2-bullseye

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR has been generated by Mend Renovate. View repository job log here.

Go auto release workflows @goruha (#20)

# What * Use go auto-release workflow `cloudposse/.github/.github/workflows/shared-go-auto-release.yml@main` * Remove `.goreleaser.yml`. Now will use https://github.com/cloudposse/.github/blob/main/.github/goreleaser.yml * Drop `auto-release.yaml`. Now will use https://github.com/cloudposse/.github/blob/main/.github/auto-release.yml and https://github.com/cloudposse/.github/blob/main/.github/auto-release-hotfix.yml

Why

• Consolidate go releases workflows pattern

Add GitHub Settings @goruha (#21)

## what - Install a repository config (`.github/settings.yaml`)

why

• Programmatically manage GitHub repo settings

0.8.0

Remove travis badge @goruha (#19)

what

• Remove travis badge

Why

• We do not use travis ci

v0.7.0

• No changes

v0.6.0

Consolidate auto-release workflow @goruha (#17)

what

• Use cloudposse/github-action-auto-release in auto-release.yaml workflow

why

• Solve old nodejs warning
• Reduce duplication of code

0.5.1

Refactored github workflows @zdmytriv (#14)

what

• Refactored github workflows

why

• Refactored github workflows

references

Upgraded to go version 1.20, added version to release artifacts and reduced final artifact sizes @zdmytriv (#13)

what

• Upgraded go version to 1.20
• Added version to release artifacts
• Added compile options to remove debug data

why

• Build with latest go version
• Reduced final artifact sizes
• Included versions into artifact names

references

0.5.0

What's Changed

• Added arm support

0.4.0 - add possibility to send msg to thread

feat: add possibility to send msg to thread (#10)

0.3.0: add github actions (#7)

* add github actions

* upload artifacts

* Update Makefile

Co-authored-by: Andriy Knysh <[email protected]>

Co-authored-by: Andriy Knysh <[email protected]>

0.2.0 Add `SLACK_CHANNEL` parameter

what

• Add SLACK_CHANNEL parameter

why

• With this feature, one webhook url can be used to send to different channels