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

build(deps): bump github.com/spf13/viper from 1.12.0 to 1.13.0 #4

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Nov 3, 2022

Bumps github.com/spf13/viper from 1.12.0 to 1.13.0.

Release notes

Sourced from github.com/spf13/viper's releases.

v1.13.0

Important: This is the last release supporting Go 1.15.

What's Changed

Exciting New Features 🎉

Enhancements 🚀

Bug Fixes 🐛

Dependency Updates ⬆️

New Contributors

Full Changelog: spf13/viper@v1.12.0...v1.13.0

Commits
  • 57cc9a0 test: fix ini tests
  • 8030d5b build(deps): bump gopkg.in/ini.v1 from 1.66.4 to 1.67.0
  • 312417a Add a DebugTo convenience funtion
  • 202060b Adds support for uint16 with GetUint16
  • 97591f0 build: fix lint violations
  • 9af8dae ci: upgrade golangci-lint
  • 7b4f2b2 ci: add Go 1.19 to CI
  • 601ec81 test: fix toml tests
  • d7f4832 build(deps): bump github.com/pelletier/go-toml/v2 from 2.0.2 to 2.0.5
  • c2f42f3 build(deps): bump github.com/subosito/gotenv from 1.4.0 to 1.4.1
  • 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 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 [github.com/spf13/viper](https://github.com/spf13/viper) from 1.12.0 to 1.13.0.
- [Release notes](https://github.com/spf13/viper/releases)
- [Commits](spf13/viper@v1.12.0...v1.13.0)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Nov 3, 2022

The following labels could not be found: kind/dependencies.

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Nov 3, 2022

Looks like github.com/spf13/viper is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Nov 3, 2022
@dependabot dependabot bot deleted the dependabot/go_modules/github.com/spf13/viper-1.13.0 branch November 3, 2022 03:12
morlay pushed a commit that referenced this pull request Apr 10, 2024
* Initial commit

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* Initial version (#1)

Initial version of the SDK
---------

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* Clean up build process & better samples (#2)

* build: clean up build

update pom.xml dependency management
remove unused dependencies
remove unused import

* build: Add maven exec plugin to run the code samples from the CLI

* build: support dependency caching in github action (#3)

* fix: add missing sample in the sample code demo app (#4)

* feat(log): add debug log when response is contains errors. (#5)

Set the log level to debug in integration tests

* fix: support macos arm64 architure by cli downloader (#7)

* fix: client hangs on close (#8)

fix(connection): refactoring of the engine connection package

Move CLIRunner and ConnectParams to a dedicated class file
Replace JSON-B by JSON-P to deserialize the connection parameters
Move the Dagger CLI process execution to the CLI runner (Single-responsibility principle)
Fix process hanging when connection to the engine failed
Improve code style
Add some tests for Connection class

---------

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* build(workflow): enable build on linux and macos (#9)

macos is limited to PR builds
So far windows VM does not support Linux containers

Signed-off-by: Jean-Christophe Sirot <jean-christophe.sirot@docker.com>

* build: package jar with dependencies and upload artifacts in github (dagger#11)

package jar with dependencies and upload artifact in github
upload artifact only on push to main
update README.md
---------

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* Move all files into sdk/java subdir

So that this can be imported into dagger/dagger repository

Signed-off-by: Gerhard Lazu <gerhard@dagger.io>

* sdk(java): Add experimental warning to README

Signed-off-by: Gerhard Lazu <gerhard@dagger.io>

* sdk(java): Rename LICENSE

But keep as is, same as we did for other experimental SDKs.

Signed-off-by: Gerhard Lazu <gerhard@dagger.io>

* chore: Add /sdk/java to CODEOWNERS

Signed-off-by: Gerhard Lazu <gerhard@dagger.io>

* build: rename package name from 'org.chelonix.dagger.*' to 'io.dagger.*'

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* build(codegen): add introspection query in the codegen plugin resources and use it when schema is not available. Inject the CLI version in the code at build time

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* build: add linter plugin and lint current code

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* build: set development version to 1.0.0-SNAPSHOT. Add "release" profile dedicated to deployment

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* fix: correctly return the dagger CLI path in codegen plugin and fix some log messages

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* build: Add schema for 0.6.4

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* fix: fix coding style for linter

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* build: fix maven versions plugin groupId

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* ci: add java sdk CI
- add initial build worflow in internal/mage/sdk/java.go
- add test & lint actions in github action worflow

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* fix: replace deprecated API calls in tests
- Container.fs -> Container.rootfs
- Container.exec -> Container.withExec

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* fix: Add a static 'from' method to instanciate a Scalar from a String literal

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* fix(doc): fix javadoc for field parameters in generated code

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* fix: Fix NPE when CLI download fails and log error

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* fix(codegen): clarify codegen plugin parameters and Dagger version in generated code

Separate CLI and SDK version
Use either a previously generated schema or a query a locally installed dagger CLI
update the CI to generate the schema matching the used dagger CLI

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* fix(codegen): fix sdk:java:generate goal

Now the generate goal will query the dagger CLI to generate the API JSON schema and write a file
A new dagger-codegen:generateSchema plugin goal has been added to the  dagger-codegen maven plugin (with some code refactoring between both goals) to generate the schema. The generate schema is copied to plugin resources dir /schemas according to the engine version declared in the pom.xml file afterwards.
The schema file naming has been simplifying (removing the 'v' prefix) and the existing files have been renamed accordingly

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* feat(codegen): add schema for dagger engine 0.8.3 and 0.8.4

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* doc(codegen): document how to bump engine dependency

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

* Remove redundant return & go fmt

Signed-off-by: Gerhard Lazu <gerhard@dagger.io>

* Make Java SDK workflow standalone, same as the Elixir one

Leverage the re-usable _hack_make workflow.

Signed-off-by: Gerhard Lazu <gerhard@dagger.io>

* Use same Apache 2.0 license as all other SDKs

Engine & CLI use the same Apache 2.0 license.

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>

---------

Signed-off-by: Jean-Christophe Sirot <jcsirot@gmail.com>
Signed-off-by: Jean-Christophe Sirot <jean-christophe.sirot@docker.com>
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
Signed-off-by: Jean-Christophe Sirot <470082+jcsirot@users.noreply.github.com>
Co-authored-by: Jean-Christophe Sirot <jcsirot@gmail.com>
Co-authored-by: Jean-Christophe Sirot <470082+jcsirot@users.noreply.github.com>
Co-authored-by: Daniel Lavoie <dlavoie@live.ca>
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.

0 participants