Skip to content

Releases: ohnosequences/sbt-s3-resolver

sbt-s3-resolver v0.19.0

17 Oct 15:25
Compare
Choose a tag to compare
  • #57: Changed awsProfile type to Option[String] and changed s3region and s3credentials defaults to depend on it (by @tsuyoshizawa):

    By default awsProfile is set to None which means that both region and credentials will be set from the default provider chains.
    And if you change it, s3region and s3credentials will both use given profile region and credentials.

    This makes these two settings more consistent, but also introduces a potentially breaking change: if you used some unusual setting for s3region or s3credentials, check their values after this update:

    > show s3region
    > showS3Credentials
    
  • This release also deprecates conversions related to credential providers: | for chaining and implicit conversion from File. Use AWS Java SDK explicitly instead.

sbt-s3-resolver v0.18.0

26 Sep 10:13
Compare
Choose a tag to compare
  • #55: Changed s3acl type to Option[S3ACL]: when it's unset, artifacts will be published inheriting the bucket ACL (by @hkupty)

sbt-s3-resolver v0.17.1

25 Sep 12:22
Compare
Choose a tag to compare

This is a bugfix release, it updates to ivy-s3-resolver v0.12.0 which solves the problem with redundant delimiters the ivy-style patterns introduced in sbt 1.0 (see sbt/sbt#3573).

The problem was reported and handled in the underlying library by Michael Ahlers @michaelahlers:

sbt-s3-resolver v0.17.0

19 Sep 03:35
Compare
Choose a tag to compare

IMPORTANT

This release is affected by the problem with redundant delimiters in the ivy-style patterns introduced in sbt 1.0 (see sbt/sbt#3573). You are strongly recommended to update to the next version which contains a fix for it.

sbt-s3-resolver v0.16.0

14 Jun 18:46
Compare
Choose a tag to compare
  • Updates for compatibility with EU Frankfurt AWS Region (See #49 & #47)
  • Updated ivy-resolver dependency (with important updates to AWS Java SDK)
  • Fixed how toHttps method works for different regions with different endpoint prefixes
  • Changed Region type to com.amazonaws.regions.Region
  • Changed default region setting to DefaultAwsRegionProviderChain; added implicit conversions

sbt-s3-resolver v0.15.0

17 Aug 15:41
Compare
Choose a tag to compare
  • Upgraded to the ivy-s3-resolver v0.9.0

sbt-s3-resolver v0.14.0

17 Jan 22:17
Compare
Choose a tag to compare
  • Upgraded to the ivy-s3-resolver v0.8.0 with support for server side encryption (see #46) by @pityka

sbt-s3-resolver v0.13.1

24 Sep 22:02
Compare
Choose a tag to compare
  • Updated ivy-s3-resolver to 0.7.1. It solves the Java incompatibility issue #38.

sbt-s3-resolver v0.13.0

15 Jun 15:27
Compare
Choose a tag to compare
  • It is now an auto plugin, meaning that you don't need to load any defaults and do manual imports, just add it to your project/plugins.sbt and enjoy
  • Added profile credentials provider; simplified the default providers chain:
    • profile credentials from ~/.aws/credentials (same as you use form AWS command line tools). You can choose profile by setting awsProfile key.
    • EC2 instance metadata.
  • Added s3acl Access Control List configuration parameter (which defaults to PublicRead) (thanks @anzecesar, see #36)
  • Added converter of an S3 bucket address to https

sbt-s3-resolver v0.12.0

08 Sep 16:42
Compare
Choose a tag to compare