ifsc 2.0.15 → 2.0.17
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +7 -1
- data/DOCUMENTATION.md +77 -0
- data/ifsc.gemspec +1 -1
- data/src/IFSC.json +1 -1
- metadata +2 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: c3435f73c9096677b5ed44b2d341e1c92c4c512391072badfc5765074b7ab86e
|
|
4
|
+
data.tar.gz: 5f3b676cf081efde710ce12e3898c6deb2c9323e1ddab7f9fb4447d93a8a4ff6
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 187acf5d2d8adb7c8907ae8d05c20eecf564b533f9f2fbcf4d741caf931eefc15a4f91716eb517d3b7891e9585fef73cb77c7675d8d7ef05192e4d3d7e86ae49
|
|
7
|
+
data.tar.gz: 9e5fb3d999759202ef756146919c123d96239e54dd1497a770ef2f24c75e12748d1f61c480b72d07f7653ff681a94d67d8e1ba29edbd2622cc3f2f6059c75cdd
|
data/CHANGELOG.md
CHANGED
|
@@ -5,10 +5,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
5
5
|
|
|
6
6
|
## [UNRELEASED][unreleased]
|
|
7
7
|
|
|
8
|
-
## [2.0.
|
|
8
|
+
## [2.0.17][2.0.17]
|
|
9
9
|
### Changed
|
|
10
10
|
- Metadata updates
|
|
11
11
|
|
|
12
|
+
## [2.0.16][2.0.16]
|
|
13
|
+
### Changed
|
|
14
|
+
- Metadata updates
|
|
15
|
+
- Automated SDK Releases
|
|
16
|
+
- Added Documentation
|
|
17
|
+
|
|
12
18
|
## [2.0.14][2.0.14]
|
|
13
19
|
### Changed
|
|
14
20
|
- Metadata updates
|
data/DOCUMENTATION.md
ADDED
|
@@ -0,0 +1,77 @@
|
|
|
1
|
+
## Check whether a new release is required
|
|
2
|
+
1. Whenever a change in detected on the RBI website (https://www.rbi.org.in/Scripts/bs_viewcontent.aspx?Id=2009), an automated email from the "RBI Updates" is sent on the "#tech_ifsc" Slack channel.
|
|
3
|
+
2. Open the website it has detected change and compare the RBI release date with the `RBI Update Date` of the latest release. If the release date and update date differ, make a new release.
|
|
4
|
+
|
|
5
|
+
## Publish a new release of IFSC repository (https://github.com/razorpay/ifsc)
|
|
6
|
+
1. Clone the IFSC repository (https://github.com/razorpay/ifsc) locally.
|
|
7
|
+
2. Create a new `release/{version}` branch. The branch name must be `release/x.y.z`. Start with a patch version bump unless you are making code level changes, in which case you can use a minor/major version bump.
|
|
8
|
+
3. Grep for the current version in the codebase. Bump the versions in `package.json`, `ifsc.gemspec`. Do not change it in `package-lock.json`.
|
|
9
|
+
4. Update `CHANGELOG.md` with the appropriate description.
|
|
10
|
+
5. Commit this as `[release] x.y.z`. Push these changes to the IFSC repository (https://github.com/razorpay/ifsc).
|
|
11
|
+
6. Github Actions are run automatically and under the "Scraper" Action, download the artifacts produced during runtime (`release-artifact` and `release-notes.md`) from the build pipeline. Make sure all the tests (Github Actions) are passing successfully.
|
|
12
|
+
7. Extract the artifacts and copy the files `banks.json`, `IFSC.json` and `sublet.json` into the `ifsc/src/` directory.
|
|
13
|
+
8. Again, commit these changes and push it into the IFSC repository and check the tests. If something is failing, you might need to edit the constants or `banknames.json` file.
|
|
14
|
+
9. Create a new pull request with this branch. Copy the `release-notes.md` file and use that as description for the PR. Review and merge the PR. Tag the merge commit (don't use a prefix, just `X.Y.Z`).
|
|
15
|
+
10. Create a release on GitHub (https://github.com/razorpay/ifsc/releases/new).
|
|
16
|
+
- Create a new tag.
|
|
17
|
+
- Use `release-notes.md` file as the template.
|
|
18
|
+
- Replace `TODO` as applicable for the release.
|
|
19
|
+
- Upload the `release-artifact` files as part of the release.
|
|
20
|
+
11. On making a new release, Github Actions for SDK update are automatically triggered. After all the actions run successfully, the `npm`, `gem` and `php` packages are updated to the latest versions, which can be checked by the badges in the `README.md` file.
|
|
21
|
+
|
|
22
|
+
## Publish a new release of IFSC-API repository (https://github.com/razorpay/ifsc-api)
|
|
23
|
+
1. Ensure that a new gem release has been made for the latest release (https://rubygems.org/gems/ifsc).
|
|
24
|
+
2. Clone the IFSC-API repository (https://github.com/razorpay/ifsc-api) locally.
|
|
25
|
+
3. Create a new `{version}` branch. The branch name must be `x.y.z`. Start with a patch version bump unless you are making code level changes, in which case you can use a minor/major version bump.
|
|
26
|
+
4. Go to the latest IFSC release (https://github.com/razorpay/ifsc/releases).
|
|
27
|
+
5. Download and extract the `by-bank.tar.gz` file from the release assets and copy the files into the `ifsc-api/data` directory.
|
|
28
|
+
6. Run a dependency update (`bundle update && bundle update --gemfile Gemfile.build`).
|
|
29
|
+
7. Dependency update updates `Redis` package, which could break workflows. In such a case, manually edit the package version to its previous one.
|
|
30
|
+
8. Check whether the ifsc gem is updated to the latest version (`grep ifsc Gemfile.lock`).
|
|
31
|
+
9. Commit this as `[release] x.y.z`. Push these changes to the IFSC-API repository (https://github.com/razorpay/ifsc-api).
|
|
32
|
+
10. Create a new pull request with this branch. Review and merge the PR. Tag the merge commit (don't use a prefix, just `X.Y.Z`).
|
|
33
|
+
11. Create a release on GitHub (https://github.com/razorpay/ifsc-api/releases/new).
|
|
34
|
+
- Create a new tag.
|
|
35
|
+
- Add a description as applicable for the release.
|
|
36
|
+
12. Check whether a new tag has been created on docker hub (https://hub.docker.com/r/razorpay/ifsc/tags).
|
|
37
|
+
|
|
38
|
+
## Deploy the new IFSC release on X Dashboard / IFSC-API repository SDK update
|
|
39
|
+
|
|
40
|
+
1. Run `composer update razorpay/ifsc --ignore-platform-req=ext-grpc`.
|
|
41
|
+
```
|
|
42
|
+
composer update razorpay/ifsc --ignore-platform-req=ext-grpc
|
|
43
|
+
```
|
|
44
|
+
2. You will get to see something like this,
|
|
45
|
+
```
|
|
46
|
+
Your GitHub credentials are required to fetch private repository metadata (git@github.com:razorpay/hodor.git)
|
|
47
|
+
When working with _public_ GitHub repositories only, head to https://github.com/settings/tokens/new?scopes=&description=Composer+on+{...} to retrieve a token.
|
|
48
|
+
This token will have read-only permission for public information only.
|
|
49
|
+
When you need to access _private_ GitHub repositories as well, go to https://github.com/settings/tokens/new?scopes=repo&description=Composer+on+{...}
|
|
50
|
+
Note that such tokens have broad read/write permissions on your behalf, even if not needed by Composer.
|
|
51
|
+
Tokens will be stored in plain text in "/Users/{...}/.composer/auth.json" for future use by Composer.
|
|
52
|
+
For additional information, check https://getcomposer.org/doc/articles/authentication-for-private-packages.md#github-oauth
|
|
53
|
+
```
|
|
54
|
+
Go to the private repository token generation link and generate token.
|
|
55
|
+
|
|
56
|
+
3. Paste the token on terminal and press enter. You will get to see something like this,
|
|
57
|
+
```
|
|
58
|
+
Token stored successfully.
|
|
59
|
+
GitHub API token requires SSO authorization. Authorize this token at https://github.com/orgs/razorpay/sso?authorization_request={...}
|
|
60
|
+
|
|
61
|
+
After authorizing your token, confirm that you would like to retry the request
|
|
62
|
+
```
|
|
63
|
+
Go to the link to authorise.
|
|
64
|
+
|
|
65
|
+
4. Post authorising, just press `y` or write `yes` on terminal and press enter. It will update IFSC repository in API.
|
|
66
|
+
5. Commit the `composer.lock` file and raise PR. Fix any tests that fail due to the IFSC codes removed / added (need to let CI run and check required suites for failures, most of the ifsc tests are required only).
|
|
67
|
+
6. Merge and deploy.
|
|
68
|
+
|
|
69
|
+
## Deploy the new Stage IFSC release on the Stage API website (http://ifsc.stage.razorpay.in/)
|
|
70
|
+
1. Go to Spinnaker (https://deploy.razorpay.com/#/applications/stage-ifsc/executions).
|
|
71
|
+
2. Run the "stage-ifsc-infra" pipeline, by clicking on "Start Manual Execution" against it. In the parameters section, enter the latest tag number as "2.0.14" (OR) simply "latest" against the "Image tag" parameter and enter the latest kube-manifest commit ID against the "kube_manifests_commit" parameter. Take the latest commit ID from kube-manifest repository (https://github.com/razorpay/kube-manifests).
|
|
72
|
+
3. Open the "stage-ifsc" endpoint (http://ifsc.stage.razorpay.in/) and test the API by running deleted and newly added IFSC codes in the latest release.
|
|
73
|
+
|
|
74
|
+
## Deploy the new Production IFSC release on the Production API website (https://ifsc.razorpay.com/)
|
|
75
|
+
1. Go to Spinnaker (https://deploy.razorpay.com/#/applications/stage-ifsc/executions).
|
|
76
|
+
2. Run the "prod deploy" pipeline, by clicking on "Start Manual Execution" against it. In the parameters section, enter the latest tag number as "2.0.14" (OR) simply "latest" against the "Image tag" parameter.
|
|
77
|
+
3. Open the API (https://ifsc.razorpay.com/) and test the website by running deleted and newly added IFSC codes in the latest release.
|
data/ifsc.gemspec
CHANGED
|
@@ -3,7 +3,7 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
|
|
3
3
|
|
|
4
4
|
Gem::Specification.new do |s|
|
|
5
5
|
s.name = 'ifsc'
|
|
6
|
-
s.version = '2.0.
|
|
6
|
+
s.version = '2.0.17'
|
|
7
7
|
s.date = '2022-10-28'
|
|
8
8
|
s.summary = 'IFSC code database to help you validate IFSC codes'
|
|
9
9
|
s.description = 'A simple gem by @razorpay to help you validate your IFSC codes. IFSC codes are bank codes within India'
|