Tricia Decker

It looks like the [linter test](https://github.com/lyft/protoc-gen-star/runs/7847875914?check_suite_focus=true) started failing after this merge commit: https://github.com/lyft/protoc-gen-star/pull/96/commits/cd567a8de02cdc28453b8b44eaba7f50175748f2

> @pdecks When can we expect a new release with this PR? You'll need to address the error in the `pre-commit` check first.

> > > @pdecks When can we expect a new release with this PR? > > > > > > You'll need to address the error in the `pre-commit` check...

> For some reason, I am unable to see the errors outputted by my module when checking the protobuf inputs for correctness. Is there currently a way to do this?...

Thanks for the feedback! Will make a note to add some documentation / a walkthrough. The basic steps are: 1. Create the `.bin` using `protoc-gen-debug` 2. In your test file,...

You're welcome! > I am not passing the AST to my module; I don't think I need to do this as I am embedding `*pgs.ModuleBase` in my module and my...

I created https://github.com/nilslice/protolock/pull/151 expanding on https://github.com/YaseenAlk/protolock/commit/287eb47dd9a03aa39a30619d34810b3a637f95b7 and also added a rule utilizing the new field to prevent backwards-incompatible Go changes per https://google.aip.dev/180#moving-into-oneofs.

Closing this since testing was never added and because `"import_path"` and `"import_prefix"` have since been deprecated and [removed](https://github.com/protocolbuffers/protobuf-go/commit/8b366e880709d9be636fad37fdab80990e7effc9) from protoc-gen-go.

Closing this since it is obsolete given we migrated to protobuf APIv2, which deprecated `import_path`. See https://github.com/protocolbuffers/protobuf-go/commit/3e80249d38abc90bd0de433b139c8b6f803503d3

I ended up reverting the other changes that warranted the v2 releases and cut a v0.6.2 release with your post-processor changes. Note that we will no longer be supporting v0...