Skip to content

Releases: djspiewak/sbt-github-packages

v0.5.3

24 May 04:12
v0.5.3
Compare
Choose a tag to compare
  • Swapped publication upstream from Bintray to Maven Central

v0.5.2

30 May 18:00
v0.5.2
Compare
Choose a tag to compare
  • Fixed a bug which caused a cyclic reference between githubPublishTo and publishTo

v0.5.1

24 May 18:03
v0.5.1
9e24b6d
Compare
Choose a tag to compare
  • Factored publication settings out into a githubPublishTo key, which can help composing this plugin with other publication plugins such as sbt-sonatype. (@xerial)
  • Documentation fixes and improvements (@sergiuszkierat)

v0.5.0

16 Mar 05:38
v0.5.0
Compare
Choose a tag to compare
  • Removed githubActor setting. It was kind of pointless, since the GitHub API doesn't actually verify username, only token. The username _ is now used for all API operations.
  • Added fallbacks for scmInfo and homepage when githubRepository and githubOwner are left unspecified.
  • Exposed TokenSource resolution via the GitHubPackagesPlugin.resolveTokenSource function. Before this, the only way to get access to this functionality was to call inferredGitHubCredentials, cast to DirectCredentials, and then invoke passwd on the result, which was unpleasant to say the least.

v0.4.2

07 Mar 05:15
v0.4.2
Compare
Choose a tag to compare
  • Added githubSuppressPublicationWarning to better support resolver use-cases that don't want to see the publication warning.

v0.4.1

07 Mar 00:53
v0.4.1
Compare
Choose a tag to compare
  • #13 - Fixed SCM url to properly have the trailing .git (@mkurz)

v0.4.0

03 Mar 19:09
v0.4.0
Compare
Choose a tag to compare

As a note, sbt-github-packages is now underlying the artifact infrastructure for SlamData, and it appears to be working quite well! To that end, I am no longer considering this plugin to be in pre-release status, since it is literally driving a production application. More changes (specifically to the use of GITHUB_ACTOR) are likely coming in the future and will be versioned appropriately, but things are stable enough now that I consider it a viable choice for package publication in sbt.

  • Changed default token/user sources to environment variables: GITHUB_TOKEN and GITHUB_ACTOR. I misunderstood the GitHub Actions documentation (such as it is…) and that was the source of the confusion. Sorry everyone!
  • Defaulted the repo parameter of the Resolver to _, since it doesn't appear to matter what repository you name in the resolver! This is actually really helpful and nice and, arguably, the way that Packages should be behaving. It's just not documented anywhere.
  • Added check (and error) when someone attempts to do publishMavenStyle := false, since it will silently fail to fully publish, resulting in errors during resolution.

v0.3.1

19 Feb 23:23
v0.3.1
Compare
Choose a tag to compare
  • Added || combinator to TokenSource, allowing you to define a priority list of possibilities to check

v0.3.0

06 Feb 04:47
v0.3.0
Compare
Choose a tag to compare
  • Removed requisite ThisBuild / scoping. Usage should now be a lot more uniform with other publication plugins
  • Renamed some keys (such as githubActor) to be a bit more conventional
  • Adjusted default token/actor sources to work out of the box with GitHub Actions
  • Removed optionality to the TokenSource. Apparently authentication is required even for public packages, which is inane

v0.2.1

08 Dec 22:41
v0.2.1
Compare
Choose a tag to compare

Removed the realm name conflict by simply renaming the added resolvers. All stated functionality in the plugin now works and has been tested.