parse_packwerk 0.10.0 → 0.10.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 00ce04288d8a8c4f46571bd181e8a3781d325116cd58e8078cdf142e9f74ffce
-  data.tar.gz: 23c1e53eab84fc472d116bf025c6ddb499f509da25246f47ffbdb857ec922f3f
+  metadata.gz: f409f199bdc5359f8287eeb77ddc83b47ee35d98d7066af8d11dafa1dda0f23b
+  data.tar.gz: 2a0978ce08554183ec20865f64bfc6480d7d9501ca015130589d4f20a75bcf72
 SHA512:
-  metadata.gz: f24bf1e21e1800e35aa9c4fcdbf1c5e71efafd421d1ce7829461e620c30728a23dd78e099f91bd359fa69e0bca9cef71fabea4cc139598520520942afbcf9006
-  data.tar.gz: 6bd309198e121db0066178ec0fcddbef4b0187110a600bc716fe72d1ebbedab713767b25700d679bd219cafabd93ce6c0896cc0cf9cfa51c279c205105c30003
+  metadata.gz: 4c9338e22916f759cbe982087f52606eaec69ff4fcbd4bbc90bb8f1c2787e1cfa08fce8e678f70edd5ae2566e0afa1ba8aa65e3039706bfe7390ad8b1b2d3853
+  data.tar.gz: 9fe7860d98c05d3049b902f2a3bd0c04c1b69568195e385c00ae756883b7b48d52da9decd6f5cd1c2b848daf1414de5a99e6461fdafc95265ec09c202eddb128

data/README.md

@@ -26,8 +26,8 @@ We generally recommend folks depend on `packwerk` rather than `parse_packwerk`.
 
 This gem exists for this toolchain for these reasons:
 
-(A) `packwerk` is lacking public APIs for the behavior we want. It's close with `PackageSet`, but we need to also be able to parse violations.
-(B) Certain critical, production runtime code-paths need to use this, and we want a simple, low-dependency, infrequently changing dependency for our production environment. One example of production usage is that `package.yml` files can store team ownership information, which is used when an error happens in production to route it to the right team.
-(C) `packwerk` has heavy duty dependencies like rails and lots of others, and it adds a degree of maintenance cost and complexity that isn’t necessary when all we want to do is read YML files
+- `packwerk` is lacking public APIs for the behavior we want. It's close with `PackageSet`, but we need to also be able to parse violations.
+- Certain critical, production runtime code-paths need to use this, and we want a simple, low-dependency, infrequently changing dependency for our production environment. One example of production usage is that `package.yml` files can store team ownership information, which is used when an error happens in production to route it to the right team.
+- `packwerk` has heavy duty dependencies like rails and lots of others, and it adds a degree of maintenance cost and complexity that isn’t necessary when all we want to do is read YML files
 
 Long-term, it might make sense for these reasons to extract out some of the parsing from `packwerk` into a separate gem similar to this so that we can leverage the ecosystem of tools associated with the idea of a “pack” in ways that are simple and safe for both development and production environments.

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: parse_packwerk
 version: !ruby/object:Gem::Version
-  version: 0.10.0
+  version: 0.10.1
 platform: ruby
 authors:
 - Gusto Engineers
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-05-03 00:00:00.000000000 Z
+date: 2022-06-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: sorbet-runtime
@@ -141,13 +141,13 @@ files:
 - sorbet/rbi/gems/hashdiff@1.0.1.rbi
 - sorbet/rbi/gems/rspec@3.10.0.rbi
 - sorbet/rbi/gems/rspec_override.rbi
-homepage: https://github.com/bigrails/parse_packwerk
+homepage: https://github.com/rubyatscale/parse_packwerk
 licenses:
 - MIT
 metadata:
-  homepage_uri: https://github.com/bigrails/parse_packwerk
-  source_code_uri: https://github.com/bigrails/parse_packwerk
-  changelog_uri: https://github.com/bigrails/parse_packwerk/releases
+  homepage_uri: https://github.com/rubyatscale/parse_packwerk
+  source_code_uri: https://github.com/rubyatscale/parse_packwerk
+  changelog_uri: https://github.com/rubyatscale/parse_packwerk/releases
   allowed_push_host: https://rubygems.org
 post_install_message: 
 rdoc_options: []