chore(deps): bump amannn/action-semantic-pull-request (#68)

Bumps the dependencies group with 1 update: [amannn/action-semantic-pull-request](https://github.com/amannn/action-semantic-pull-request).


Updates `amannn/action-semantic-pull-request` from 6.0.1 to 6.1.0
- [Release notes](https://github.com/amannn/action-semantic-pull-request/releases)
- [Changelog](https://github.com/amannn/action-semantic-pull-request/blob/main/CHANGELOG.md)
- [Commits](amannn/action-semantic-pull-request@fdd4d3d...7f33ba7)

---
updated-dependencies:
- dependency-name: amannn/action-semantic-pull-request
  dependency-version: 6.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

chore(deps): bump docker/login-action in the dependencies group (#64)

chore(deps): bump docker/build-push-action in the dependencies group (#…

…60)

chore(deps): bump docker/build-push-action in the dependencies group (#…

…60)

feat: major version updater (#55)

Updates the major version to point to the latest published tag with the same major tag

Example:

v2.2.0 exists
v2 is currently pointed to v2.2.0

release happens

v2.3.0 is created
this action will point v2 at the new v2.3.0

Signed-off-by: jmeridth <jmeridth@gmail.com>

chore(deps): bump docker/build-push-action in the dependencies group (#…

…49)

Bumps the dependencies group with 1 update: [docker/build-push-action](https://github.com/docker/build-push-action).


Updates `docker/build-push-action` from 6.13.0 to 6.14.0
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](docker/build-push-action@ca877d9...0adf995)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

feat: ensure contents of container image changes (#46)

I got confused when the release tagging was being applied
to the same release package (container image).  This was because
the container image was not changing.

With this change, we put the contents of the repo into the
container image, ensuring there is change and a new image and digest
is created.  This will also cause new attestation to be created.

- [x] remove .github folder from .dockerignore to ensure the folder is put into the container image
- [x] update README explaining what the image contents are and why

Signed-off-by: jmeridth <jmeridth@gmail.com>

fix: put argument in correct section, config, not secrets (#44)

Signed-off-by: jmeridth <jmeridth@gmail.com>

ci: remove attestations temporarily (#41)

Unfortunately attestations are causing confusion in the image registry.  Need
to resolve that before putting it back.

Signed-off-by: jmeridth <jmeridth@gmail.com>

ci: reduce permissions on auto-labeler and set to not release (#38)

We were seeing random draft releases after a release occurred. I
realized the auto-labeler workflow (also using draft-release action)
was still doing a draft release.  This was the culprit.  By adding
`disable-releaser: true`, we prevent this.  Since this workflow no
longer needs to create a release we can remove the `contents: write`
permissions also.

- [x] change image-name from hard-coded to github.repository in test-release

Signed-off-by: jmeridth <jmeridth@gmail.com>