darjeelink 0.14.6 → 0.14.8
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +1 -22
- data/config/initializers/darjeelink.rb +1 -0
- data/lib/darjeelink/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: fe18ade1a67f8f92f09f7e95ea71d8bb27bfe1ac9604be8dd4e62b0156b987b7
|
|
4
|
+
data.tar.gz: 616617118a3317479035593d85daeed19ad7b538ca27a54cd5a1861d2e80f631
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: bebc83488bca28c7291c095d24b0ae3cacddf8a07e28fb2db332e99ed4dcc3b0236ff8b63c8dc70289af2e0203bd6fb59d004b8d463d8d2b2c47f8a04e385376
|
|
7
|
+
data.tar.gz: '088614333aa05239f7c819b5acbad2115fd6728a4245b5228c69e3cccc617f4ce541a1d898113ffa7c199847fa88ccb899128bbd93f849c9beae904ddce0a047'
|
data/README.md
CHANGED
|
@@ -120,28 +120,7 @@ Change the database url to be different to the development one i.e. `postgres://
|
|
|
120
120
|
## Releasing
|
|
121
121
|
Darjeelink follows [Semantic Versioning](https://semver.org)
|
|
122
122
|
|
|
123
|
-
|
|
124
|
-
There are several ways to test the gem before releasing it.
|
|
125
|
-
|
|
126
|
-
One way, is to check the new development branch into Github, and then use `portkey-app` to test it in a staging environment.
|
|
127
|
-
|
|
128
|
-
- Create a new branch in the `darjeelink` repo with a sensible name related to your intended release: e.g. `darjeelink-v0.14.6-upgrade`.
|
|
129
|
-
- Perform the required upgrades, security patching, etc for the new release.
|
|
130
|
-
- Bump the version number as required (see below).
|
|
131
|
-
- Create a new branch in the `portkey-app` repo with a sensible name related to your intdended release: e.g. `darjeelink-v0.14.6-upgrade`.
|
|
132
|
-
- In the `Gemfile` of the portkey-app repo, change the `darjeelink` gem to point to the branch you just created in the darjeelink repo.
|
|
133
|
-
```gemfile
|
|
134
|
-
# Actual URL Shortener
|
|
135
|
-
# gem 'darjeelink' <-- Temporarilly change this. Remeber to change it back, and run bundle install to update the Gemfile.lock when done!
|
|
136
|
-
gem 'darjeelink', git: 'https://github.com/38degrees/darjeelink.git',
|
|
137
|
-
branch: 'darjeelink-v0.14.6-upgrade'
|
|
138
|
-
```
|
|
139
|
-
- Update the `Gemfile.lock` in the `portkey-app` repo by running `bundle install` and commit then push the changes.
|
|
140
|
-
- Deploy your branch of the portkey-app to the staging environment and test the changes.
|
|
141
|
-
|
|
142
|
-
NB: When you have followed the production release steps below and created a GitHub release, you can then update the `Gemfile` in the `portkey-app` repo to point to the new release tag.
|
|
143
|
-
|
|
144
|
-
### Releasing - Production
|
|
123
|
+
NB: Before releasing, ensure that the gem is working as expected by running the tests. If possible perform some manual testing via a webserver.
|
|
145
124
|
|
|
146
125
|
Once all necessary changes have made it in to master and you are ready to do a release you need to do these steps.
|
|
147
126
|
|
data/lib/darjeelink/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: darjeelink
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.14.
|
|
4
|
+
version: 0.14.8
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- James Hulme
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2024-
|
|
11
|
+
date: 2024-08-14 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: omniauth
|