Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump celestiaorg/.github from 0.2.2 to 0.3.3 #68

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 25, 2024

Bumps celestiaorg/.github from 0.2.2 to 0.3.3.

Release notes

Sourced from celestiaorg/.github's releases.

Release v0.3.3

0.3.3 (2024-03-18)

What's Changed

Full Changelog: celestiaorg/.github@v0.3.2...v0.3.3

Release v0.3.2

What's Changed

In the prior release, a commit hash was being added to the workflow run name which resulted in a new workflow each time. This release addresses that issue which requires updating the branch protection rules to target the workflow run without the hash in the name.

For Example: Screen Shot 2024-02-07 at 10 41 39 AM

The second impact to the workflows is that previously the Scaleway and Dockerhub runs would fail due to permission issues. Some team's handled this by marking these as not required in the branch protection rules. These runs will now skip instead of fail so they can be marked as required in the branch protection rules.

Full Changelog: celestiaorg/.github@v0.3.1...v0.3.2

Release v0.3.1

0.3.1 (2024-01-17)

Continuous Integration

What's Changed

Full Changelog: celestiaorg/.github@v0.3.0...v0.3.1

v0.3.0

Important

Now, it's a mandatory step to have 3 registries set up per repository that uses the new release of reusable docker workflow This means that secrets need to be added and security should be inherited so the workflow is not failing

What's Changed

Full Changelog: celestiaorg/.github@v0.2.8...v0.3.0

v0.2.8

... (truncated)

Commits
  • 1cb27a6 chore (ci): rename step within docker security job (#97)
  • 813fe47 fix: fix failing docker CI due to permission issues on PRs (#94)
  • b88ab2a ci: fix bugs in docker workflow (#90)
  • 068cf47 feat: add DockerHub and ScaleWay registries (#88)
  • 03c6f4d feat: add a simple DockerFile and runner test (#87)
  • 7bea606 feat: verify-signature.sh script (#84)
  • 98b8060 bug: fix handling of variables in conditions (#82)
  • a19b2f4 debug: remove echo statement for large object (#81)
  • f6e5547 bug: fix github.event_name error (#80)
  • daf0ee3 bug: remove buggy echo statement (#78)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [celestiaorg/.github](https://github.com/celestiaorg/.github) from 0.2.2 to 0.3.3.
- [Release notes](https://github.com/celestiaorg/.github/releases)
- [Commits](celestiaorg/.github@v0.2.2...v0.3.3)

---
updated-dependencies:
- dependency-name: celestiaorg/.github
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Mar 25, 2024
@dependabot dependabot bot requested a review from a team March 25, 2024 11:15
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.63%. Comparing base (642bb01) to head (308dba2).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #68   +/-   ##
=======================================
  Coverage   64.63%   64.63%           
=======================================
  Files           6        6           
  Lines         410      410           
=======================================
  Hits          265      265           
  Misses        109      109           
  Partials       36       36           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor Author

dependabot bot commented on behalf of github Apr 8, 2024

Superseded by #73.

@dependabot dependabot bot closed this Apr 8, 2024
@dependabot dependabot bot deleted the dependabot/github_actions/celestiaorg/dot-github-0.3.3 branch April 8, 2024 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant