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): pin dependencies #79

Merged
merged 6 commits into from
Feb 8, 2024
Merged

chore(deps): pin dependencies #79

merged 6 commits into from
Feb 8, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 3, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
actions/checkout action pinDigest -> b4ffde6
actions/setup-node action patch v4.0.0 -> v4.0.2
actions/upload-artifact action major v3.1.3 -> v4.3.1
docker/login-action action pinDigest -> 343f7c4
google-github-actions/release-please-action action major v3 -> v4

Release Notes

actions/setup-node (actions/setup-node)

v4.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: actions/setup-node@v4.0.1...v4.0.2

v4.0.1

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4...v4.0.1

actions/upload-artifact (actions/upload-artifact)

v4.3.1

Compare Source

v4.3.0

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.3.0

v4.2.0

Compare Source

What's Changed

Full Changelog: actions/upload-artifact@v4...v4.2.0

v4.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: actions/upload-artifact@v4...v4.1.0

v4.0.0

Compare Source

What's Changed

The release of upload-artifact@v4 and download-artifact@v4 are major changes to the backend architecture of Artifacts. They have numerous performance and behavioral improvements.

For more information, see the @​actions/artifact documentation.

New Contributors

Full Changelog: actions/upload-artifact@v3...v4.0.0

google-github-actions/release-please-action (google-github-actions/release-please-action)

v4

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

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

@renovate renovate bot force-pushed the renovate/githubactions branch 2 times, most recently from 4feeba2 to bd3ea0c Compare January 18, 2024 21:43
@renovate renovate bot changed the title chore(deps): update githubactions chore(deps): pin dependencies Jan 21, 2024
@renovate renovate bot force-pushed the renovate/githubactions branch 4 times, most recently from c109a02 to 527cb5d Compare January 24, 2024 07:01
@renovate renovate bot force-pushed the renovate/githubactions branch 4 times, most recently from c04b131 to 8dba68c Compare February 8, 2024 08:28
| datasource  | package                                     | from   | to     |
| ----------- | ------------------------------------------- | ------ | ------ |
| github-tags | actions/setup-node                          | v4.0.0 | v4.0.2 |
| github-tags | actions/upload-artifact                     | v3.1.3 | v4.3.1 |
| github-tags | google-github-actions/release-please-action | v3     | v4     |
Copy link
Contributor Author

renovate bot commented Feb 8, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

Copy link
Contributor

@zachariahmiller zachariahmiller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@mjnagel mjnagel merged commit bfab11e into main Feb 8, 2024
7 checks passed
@mjnagel mjnagel deleted the renovate/githubactions branch February 8, 2024 16:54
jeff-mccoy pushed a commit that referenced this pull request Feb 9, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.12.0](v0.11.1...v0.12.0)
(2024-02-09)


### Features

* introduce advancedHTTP for expose field & change podLabels to selector
([#154](#154))
([1079267](1079267))


### Miscellaneous

* **deps:** pin dependencies
([#79](#79))
([bfab11e](bfab11e))
* remove retry-action action on registry1 docker login
([#160](#160))
([eea0c93](eea0c93))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
robmcelvenny pushed a commit to owen-grady/uds-core-slim-dev that referenced this pull request Jun 3, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.12.0](defenseunicorns/uds-core@v0.11.1...v0.12.0)
(2024-02-09)


### Features

* introduce advancedHTTP for expose field & change podLabels to selector
([#154](defenseunicorns/uds-core#154))
([1079267](defenseunicorns/uds-core@1079267))


### Miscellaneous

* **deps:** pin dependencies
([#79](defenseunicorns/uds-core#79))
([bfab11e](defenseunicorns/uds-core@bfab11e))
* remove retry-action action on registry1 docker login
([#160](defenseunicorns/uds-core#160))
([eea0c93](defenseunicorns/uds-core@eea0c93))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants