Git-secret: release v0.2.5

[joshrabinowitz]

There are some changes in git-secret since 0.2.4 that I think deserve a new release.

• we can fix the release to make sure there's one version of 0.2.4

• we now support directory names with spaces, which has been a long-standing issue people run into.

• the documentation surrounding gpg interoperability (an issue people seem to have problems with) has been improved, and we can improve it more. [I'll take another look at git-secret's gpg-related docs to see if we can clarify things more.]

• I've set up a github 'milestone' for 0.2.5: https://github.com/sobolevn/git-secret/milestone/7

Team, what do you think? What other issues would you like to see in the milestone?, and should we prep for a 0.2.5 release?

[joshrabinowitz]

Releasing master as 0.2.5 will fix several problems people were having with 0.2.4 including:

253 (Cannot encrypt new files unless all files are decrypted first),

244 (freebsd support),

230 (git secret hide malfunctions if not run at the root of the repository),

226 and #135 (some commands fail when there is a space in the filename, or in the path),

254 (CONTRIBUTING.md and doc updates)

[joshrabinowitz]

@simbo1905 @sobolevn do you guys want me to work up a PR for 0.2.5?
In particular I think we need to update CHANGELOG.md

[sobolevn]

It would be awesome! @joshrabinowitz

What help do you need in releasing it?

[joshrabinowitz]

@sobolevn I can prep the branch and the CHANGELOG.md but I'm not clear on the process required to actually make the release (correctly, with tags, releases for brew and apt, yum, dnf, etc).

I'll start the PR for 0.2.5 shortly.

[sobolevn]

Hm, I should write the docs for this. Since the releases are managed in different ways on different platforms.

[simbo1905]

@sobolevn I can prep the branch and the CHANGELOG.md but I'm not clear on the process required to actually make the release (correctly, with tags, releases for brew and apt, yum, dnf, etc).

I thought i understood the release process until I read contributing.md and saw some things that weren't familiar. We should definitely patch the docs this time.

[joshrabinowitz]

@simbo1905 @sobolevn can one of you patch the contributing.md docs in another PR?
Alternately you can tell me what to change in comments here and I'll apply them to this PR.

[sobolevn]

I can do it on friday / weekend.

[simbo1905]

I have found that squash-and-merge of PRs creates a clean git log on the master branch while keeping the original commits on the incoming branch. If we standardised on squash-and-merge for future PRs and used the PR number in the squash then it will be way easier to see what is in each new release.

[joshrabinowitz]

Just a bump to push these along. Remaining issues above are:

• update CONTRIBUTING.md
• release 0.2.5

We keep getting reports about silent failures with expired and revoked keys in versions 0.2.4 and before. It would be great to get 0.2.5 released, then we could get downstream maintainers to package 0.2.5.

[joshrabinowitz]

I think we simultaneously released v0.2.5
https://github.com/sobolevn/git-secret/releases
Also I see a tag for 0.2.5 and v0.2.5

[sobolevn]

I have removed my tag, it was incorrect anyway.

[sobolevn]

Auditing release

deb

Installing deploy dependencies
Successfully installed dpl-bintray-1.10.6
1 gem installed
dpl.2
Preparing deploy
dpl.3
Deploying application
[Bintray Upload] Reading descriptor file: build/deb_descriptor.json
[Bintray Upload] Creating version '0.2.5'...
[Bintray Upload] Bintray response: 201 Created. 
[Bintray Upload] Uploading file 'build/buildroot/git-secret_0.2.5_all.deb' to /git-secret_0.2.5_all.deb
[Bintray Upload] Bintray response: 201 Created. 
[Bintray Upload] Signing version with no passphrase...
[Bintray Upload] Bintray response: 200 OK. success
[Bintray Upload] Publishing version '0.2.5' of package 'git-secret'...
[Bintray Upload] Bintray response: 200 OK. 
after_deploy
0.42s$ chmod +x ".ci/after_deploy.sh" && ".ci/after_deploy.sh"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    72    0    72    0     0    179      0 --:--:-- --:--:-- --:--:--   179

rpm

Deploying application
[Bintray Upload] Reading descriptor file: build/rpm_descriptor.json
[Bintray Upload] Creating version '0.2.5'...
[Bintray Upload] Bintray response: 201 Created. 
[Bintray Upload] Uploading file 'build/buildroot/git-secret-0.2.5-1.noarch.rpm' to /git-secret-0.2.5-1.noarch.rpm
[Bintray Upload] Bintray response: 201 Created. 
[Bintray Upload] Signing version with no passphrase...
[Bintray Upload] Bintray response: 200 OK. success
[Bintray Upload] Publishing version '0.2.5' of package 'git-secret'...
[Bintray Upload] Bintray response: 200 OK. 
after_deploy
0.29s$ chmod +x ".ci/after_deploy.sh" && ".ci/after_deploy.sh"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    72    0    72    0     0    272      0 --:--:-- --:--:-- --:--:--   271

But, bintray is down for me: https://bintray.com/sobolevn/rpm/git-secret

[joshrabinowitz]

@sobolevn bintray looks like it's back up. I see the deb and rpm packages there now.

[sobolevn]

The final step is to submit the formula to brew: https://github.com/Homebrew/homebrew-core/pulls
And we are done!

Does anyone especially want to do it? If not, I can submit it tomorrow.

[joshrabinowitz]

@sobolevn I took a crack at it: https://github.com/Homebrew/homebrew-core/pull/36041

[delmendo]

I noticed you put up the new package for debian/ubuntu - but your package manifests don't list it. Can you update that so that 0.2.5 gets intalled automatically :)

[joshrabinowitz]

@delmendo is your note a duplicate of #312?
Also, what manifests are you referring to?

(currently debian only packages 0.2.3, we are seeking to get it updated to 0.2.5)