pg_sql_triggers 1.1.0 → 1.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: e72011f4407b6d60e5002202eedccf7e34c03075faebdf24301f74521e817904
4
- data.tar.gz: b9df169c3fecf2a3b5bb34bc6a8fd7c3cad9707ded4297276a9d73af3c57871c
3
+ metadata.gz: dff79b71aeff432cbe9324568f94bd358c76ca9161162f47b8513401eb783dd1
4
+ data.tar.gz: 524af402547aa3ef6be32605089e177a2cde1e7cae2548affa657c2af283cbf1
5
5
  SHA512:
6
- metadata.gz: 7868c6518becf693b0d34e28c18423220e8fb29ef6a5bf331123e6f0bec08735d1de582f49064b3140106f1906f1d4430fb569dcea1953c2204e5355552b4e89
7
- data.tar.gz: c6d7c92d4588482fe526d7e747d646e5abfcd542d094942348186719bf9b5240d85752e5a3485abe4d72fd21037d013bd155da8e8ddd388d5c36d4dfe88d5fd8
6
+ metadata.gz: e57441cf88cfd3e6deb7f9523286fbe862add9c0d07eef5ac127857c20f417b34ed4dc1a307a3c5c15012afbeb8524b566a2c5a5d0ad2b9284f60010bd7be99b
7
+ data.tar.gz: b216be1abbea025ff653cde512a309258e211443e86b049d74b37417ef1df3633559b274c78870fba8498fe4afbd36db72de11c45c446a4e80e717491fe72765
data/CHANGELOG.md CHANGED
@@ -7,6 +7,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [1.1.1] - 2025-12-31
11
+
12
+ ### Changed
13
+ - Updated git username in repository metadata
14
+
10
15
  ## [1.1.0] - 2025-12-29
11
16
 
12
17
  ### Added
data/README.md CHANGED
@@ -102,7 +102,7 @@ Three-tier permission system (Viewer, Operator, Admin) with customizable authori
102
102
 
103
103
  ## Examples
104
104
 
105
- For working examples and complete demonstrations, check out the [example repository](https://github.com/samaswin87/pg_triggers_example).
105
+ For working examples and complete demonstrations, check out the [example repository](https://github.com/samaswin/pg_triggers_example).
106
106
 
107
107
  ## Core Principles
108
108
 
@@ -125,7 +125,7 @@ See [COVERAGE.md](COVERAGE.md) for detailed coverage information.
125
125
 
126
126
  ## Contributing
127
127
 
128
- Bug reports and pull requests are welcome on GitHub at https://github.com/samaswin87/pg_sql_triggers.
128
+ Bug reports and pull requests are welcome on GitHub at https://github.com/samaswin/pg_sql_triggers.
129
129
 
130
130
  ## License
131
131
 
data/RELEASE.md CHANGED
@@ -152,7 +152,7 @@ gem search pg_sql_triggers
152
152
 
153
153
  ### 11. Create a GitHub Release (Optional but Recommended)
154
154
 
155
- 1. Go to https://github.com/samaswin87/pg_sql_triggers/releases
155
+ 1. Go to https://github.com/samaswin/pg_sql_triggers/releases
156
156
  2. Click "Draft a new release"
157
157
  3. Select the tag you just created (e.g., `v1.0.1`)
158
158
  4. Use the CHANGELOG entry as the release notes
data/docs/README.md CHANGED
@@ -61,6 +61,6 @@ When updating documentation:
61
61
 
62
62
  ## External Resources
63
63
 
64
- - [GitHub Repository](https://github.com/samaswin87/pg_sql_triggers)
65
- - [Example Application](https://github.com/samaswin87/pg_triggers_example)
64
+ - [GitHub Repository](https://github.com/samaswin/pg_sql_triggers)
65
+ - [Example Application](https://github.com/samaswin/pg_triggers_example)
66
66
  - [RubyGems](https://rubygems.org/gems/pg_sql_triggers)
@@ -132,4 +132,4 @@ You should see your trigger listed in the dashboard.
132
132
 
133
133
  ## Examples Repository
134
134
 
135
- For working examples and a complete demonstration of PgSqlTriggers in action, check out the [example repository](https://github.com/samaswin87/pg_triggers_example).
135
+ For working examples and a complete demonstration of PgSqlTriggers in action, check out the [example repository](https://github.com/samaswin/pg_triggers_example).
data/docs/kill-switch.md CHANGED
@@ -422,21 +422,21 @@ All kill switch events are logged with comprehensive information.
422
422
  Operation was prevented:
423
423
 
424
424
  ```
425
- [KILL_SWITCH] BLOCKED: operation=trigger_migrate environment=production actor=CLI:ashwin reason=no_override
425
+ [KILL_SWITCH] BLOCKED: operation=trigger_migrate environment=production actor=CLI:samaswin reason=no_override
426
426
  ```
427
427
 
428
428
  #### OVERRIDDEN
429
429
  Operation allowed with valid override:
430
430
 
431
431
  ```
432
- [KILL_SWITCH] OVERRIDDEN: operation=trigger_migrate environment=production actor=CLI:ashwin source=env_with_confirmation confirmation=EXECUTE TRIGGER_MIGRATE
432
+ [KILL_SWITCH] OVERRIDDEN: operation=trigger_migrate environment=production actor=CLI:samaswin source=env_with_confirmation confirmation=EXECUTE TRIGGER_MIGRATE
433
433
  ```
434
434
 
435
435
  #### ALLOWED
436
436
  Operation allowed (not in protected environment):
437
437
 
438
438
  ```
439
- [KILL_SWITCH] ALLOWED: operation=trigger_migrate environment=development actor=CLI:ashwin reason=not_protected_environment
439
+ [KILL_SWITCH] ALLOWED: operation=trigger_migrate environment=development actor=CLI:samaswin reason=not_protected_environment
440
440
  ```
441
441
 
442
442
  ### Audit Information
@@ -31,6 +31,6 @@ Next steps:
31
31
 
32
32
  5. Visit http://localhost:3000/pg_sql_triggers to access the UI
33
33
 
34
- For more information, see: https://github.com/samaswin87/pg_sql_triggers
34
+ For more information, see: https://github.com/samaswin/pg_sql_triggers
35
35
 
36
36
  ===============================================================================
@@ -11,5 +11,5 @@
11
11
  # 3. Run: bundle exec rake release
12
12
  # See RELEASE.md for detailed release instructions
13
13
  module PgSqlTriggers
14
- VERSION = "1.1.0"
14
+ VERSION = "1.1.1"
15
15
  end
metadata CHANGED
@@ -1,14 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: pg_sql_triggers
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.1.0
4
+ version: 1.1.1
5
5
  platform: ruby
6
6
  authors:
7
- - samaswin87
8
- autorequire:
7
+ - samaswin
9
8
  bindir: exe
10
9
  cert_chain: []
11
- date: 2025-12-29 00:00:00.000000000 Z
10
+ date: 1980-01-02 00:00:00.000000000 Z
12
11
  dependencies:
13
12
  - !ruby/object:Gem::Dependency
14
13
  name: pg
@@ -269,16 +268,15 @@ files:
269
268
  - lib/tasks/trigger_migrations.rake
270
269
  - scripts/generate_coverage_report.rb
271
270
  - sig/pg_sql_triggers.rbs
272
- homepage: https://github.com/samaswin87/pg_sql_triggers
271
+ homepage: https://github.com/samaswin/pg_sql_triggers
273
272
  licenses:
274
273
  - MIT
275
274
  metadata:
276
- homepage_uri: https://github.com/samaswin87/pg_sql_triggers
277
- source_code_uri: https://github.com/samaswin87/pg_sql_triggers
278
- changelog_uri: https://github.com/samaswin87/pg_sql_triggers/blob/main/CHANGELOG.md
279
- github_repo: ssh://github.com/samaswin87/pg_sql_triggers
275
+ homepage_uri: https://github.com/samaswin/pg_sql_triggers
276
+ source_code_uri: https://github.com/samaswin/pg_sql_triggers
277
+ changelog_uri: https://github.com/samaswin/pg_sql_triggers/blob/main/CHANGELOG.md
278
+ github_repo: ssh://github.com/samaswin/pg_sql_triggers
280
279
  rubygems_mfa_required: 'true'
281
- post_install_message:
282
280
  rdoc_options: []
283
281
  require_paths:
284
282
  - lib
@@ -293,8 +291,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
293
291
  - !ruby/object:Gem::Version
294
292
  version: '0'
295
293
  requirements: []
296
- rubygems_version: 3.5.22
297
- signing_key:
294
+ rubygems_version: 4.0.3
298
295
  specification_version: 4
299
296
  summary: A PostgreSQL Trigger Control Plane for Rails
300
297
  test_files: []