search

cossio / RestrictedBoltzmannMachines.jl

Train and sample Restricted Boltzmann machines in Julia
MIT License
15 stars 3 forks source link

Bump the all-deps group across 1 directory with 4 updates #52

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 4 months ago

Bumps the all-deps group with 4 updates in the / directory: actions/checkout, julia-actions/setup-julia, julia-actions/cache and julia-actions/julia-runtest.

Updates actions/checkout from 4.1.4 to 4.1.7

Release notes

Sourced from actions/checkout's releases.

v4.1.7

What's Changed

New Contributors

Full Changelog: https://github.com/actions/checkout/compare/v4.1.6...v4.1.7

v4.1.6

What's Changed

Full Changelog: https://github.com/actions/checkout/compare/v4.1.5...v4.1.6

v4.1.5

What's Changed

Full Changelog: https://github.com/actions/checkout/compare/v4.1.4...v4.1.5

Changelog

Sourced from actions/checkout's changelog.

Changelog

v4.1.7

v4.1.6

v4.1.5

v4.1.4

v4.1.3

v4.1.2

v4.1.1

v4.1.0

v4.0.0

v3.6.0

v3.5.3

... (truncated)

Commits


Updates julia-actions/setup-julia from 2.0.0 to 2.2.0

Release notes

Sourced from julia-actions/setup-julia's releases.

v2.2.0 - New lts and pre named version specifiers

What's Changed

It is now possible to specify two new named version identifiers:

  • lts for the Long Term Support (LTS) julia version (currently 1.6)
  • pre for the latest pre-release

PRs

New Contributors

Full Changelog: https://github.com/julia-actions/setup-julia/compare/v2.1.0...v2.2.0

v2.1.0

What's Changed

... (truncated)

Commits
  • 3645a07 Add production dependencies & build
  • d56bd39 Add production dependencies & build
  • c7aa298 update version 2.0.0 -> 2.2.0 (#255)
  • cae3c21 Make the devdocs more complete and self-contained (#252)
  • 389de5c Allow lts for the LTS, and allow pre for the latest pre-release (#234)
  • 42e03d3 CI: Install the same version of NodeJS that is specified in .tool-versions ...
  • e62bf8c Bump ts-jest from 29.1.2 to 29.1.5 (#249)
  • 3003881 Bump prettier from 3.2.5 to 3.3.2 (#247)
  • 0e4b558 Bump semver from 7.6.0 to 7.6.2 (#244)
  • 3599cbd Bump @​types/node from 20.12.8 to 20.14.6 (#254)
  • Additional commits viewable in compare view


Updates julia-actions/cache from 1.5.2 to 2.0.1

Release notes

Sourced from julia-actions/cache's releases.

v2.0.1

What's Changed

Full Changelog: https://github.com/julia-actions/cache/compare/v2.0.0...v2.0.1

v2.0.0

Breaking Changes ⚠️

v2.0.0 requires node20. This is a breaking change, because node20 does not support the following operating systems:

  • Red Hat Enterprise Linux 7
  • CentOS 7
  • Oracle Linux 7
  • Debian 9
  • Ubuntu 16.04
  • Linux Mint 18
  • openSUSE 15
  • SUSE Enterprise Linux (SLES) 12 SP2
  • Windows 7 64-bit
  • Windows 8.1 64-bit

Therefore, if you are using self-hosted runners on one of the above operating systems, you won't be able to run v2 of this action.

In contrast, v1 of this action uses node16.

What's Changed

New Contributors

... (truncated)

Changelog

Sourced from julia-actions/cache's changelog.

Making a new release

In this guide, as an example, v2.2.0 refers to the version number of the new release that you want to make.

Part 1: Use the Git CLI to create and push the Git tags

Step 1: Create a new lightweight tag of the form vMAJOR.MINOR.PATCH.

git clone git@github.com:julia-actions/cache.git
cd cache
git fetch --all --tags

git checkout main


git --no-pager log -1


Take note of the commit hash here.


Now, create a new lightweight tag of the form vMAJOR.MINOR.PATCH.




Replace commit_hash with the commit hash that you obtained from the


git log -1 step.




Replace v2.2.0 with the actual version number that you want to use.


git tag v2.2.0 commit_hash

Step 2: Once you've created the new release, you need to update the v2 tag to point to the new release. For example, suppose that the previous release was v2.1.0, and suppose that you just created the new release v2.2.0. You need to update the v2 tag so that it points to v2.2.0. Here are the commands:

# Create/update the new v2 tag locally, where the new v2 tag will point to the
# release that you created in the previous step.
#
# Make sure to change `v2.2.0` to the actual value for the tag that you just
# created in the previous step.
#
# The `-f` flag forcibly overwrites the old
# `v2` tag (if it exists).
git tag -f v2 v2.2.0

Step 3: Now you need to push the tags:

# Regular-push the new `v2.2.0` tag:
git push origin tag v2.2.0

Force-push the new v2 tag:


git push origin tag v2 --force

... (truncated)

Commits
  • 580d2b6 Fix issues with custom cache eviction (#135)
  • e00c08a README: document that Bash is required (#132)
  • bb4225b Devdocs: document the process for making a new release of this action (#128)
  • 8dfc57d Bump actions/checkout from 4.1.4 to 4.1.6 (#133)
  • 3190fc8 Fix typo in cache-name note (#130)
  • 2185d31 Update README to recommend julia-actions/cache@v2 (instead of @v1) (#129)
  • d48542b Bump actions/cache from 3.3.3 to 4.0.2 (#123)
  • caa6556 Bump pyTooling/Actions from 1.0.1 to 1.0.5 (#127)
  • 1c20782 Bump actions/checkout from 4.1.2 to 4.1.4 (#126)
  • 4b23ab7 update setup-julia to v2 in readme (#124)
  • Additional commits viewable in compare view


Updates julia-actions/julia-runtest from 1.9.3 to 1.10.0

Commits
  • d0c4f09 Bump julia-actions/setup-julia from 2.0.0 to 2.2.0 (#115)
  • 0c52394 hide the harness stack trace on failure (#116)
  • cee4ae9 Bump actions/checkout from 4.1.4 to 4.1.7 (#114)
  • 8b51a9e CI: Only run Dependabot once per month, but make the open-PR-limit very large...
  • 6f3702d Upgrade Codecov, and use a Codecov token (#112)
  • 93eeac9 Bump julia-actions/setup-julia from 1.9.5 to 2.0.0 (#110)
  • d07fe01 Bump actions/cache from 3.3.2 to 4.0.2 (#104)
  • e9ab5aa Bump actions/checkout from 4.1.1 to 4.1.4 (#109)
  • 7e64b54 Support specifying allow_reresolve (#107)
  • 3a055a9 Use julia-actions/cache in README example (#99)
  • Additional commits viewable in compare view


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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 3 months ago

Superseded by #53.