Update fog-core requirement from < 2.5 to < 2.7 #634
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
|
@dependabot recreate |
Updates the requirements on [fog-core](https://github.com/fog/fog-core) to permit the latest version. - [Changelog](https://github.com/fog/fog-core/blob/master/changelog.md) - [Commits](fog/fog-core@v1.20.0...v2.6.0) --- updated-dependencies: - dependency-name: fog-core dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/bundler/fog-core-lt-2.7
branch
from
aafdbc3 to
6da6ef2
Compare
|
@Temikus Do you know what's up with CI here? Can we rerun this? |
|
@stanhu sadly we have ran out of CI funding, so we cannot keep it running 😞 Until then we need to ask people to run integration tests in their own account or wait until we get back up and running again. |
|
@Temikus Is there a reason these runners can't just use the runners available for open source projects? If you need GCP runners, I'd be happy to port these integration tests to run on GitLab CI. |
|
@stanhu so the problem is not in the runners - if you notice the Unit tests run on those. The problem is that integration tests require spinning up actual infrastructure in a GCP project and all of those operations add up, even with good cleanup. The runners are local just so we use a more secure approach and use authorized workloads instead of keeping a service account key in the GitHub org. So we either need some sponsorship / GCP credits to run it ourselves or someone to donate a project with billing. And we cannot really get away with a lot of mocking and unit tests (we tried in the past) because GCP API's and libs change often in subtle ways, often breaking the gem. |
|
Ok, for now, I just went ahead and submitted #636 and ran the tests locally. |
Updates the requirements on fog-core to permit the latest version.
Changelog
Sourced from fog-core's changelog.
... (truncated)
Commits
fbcb048v2.6.0c6bbad9bump excon to 1.0 (#304)c0123baProvide a 'Changelog' link on rubygems.org/gems/fog-core (#303)4420ce6v2.5.072de8f7Exclude spec files from gem package (#302)d60548aFix frozen string literal issue for ruby 3.4 (#300)767f353bump rubocop target to 3.0 (#301)5560d23remove stale action95a7cdeadd permissions info to ci action63883a7cleanup labels and comments in ci workflow (#299)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)