Stephen Haberman

:tada: This PR is included in version 1.169.1 :tada: The release is available on: - [npm package (@latest dist-tag)](https://www.npmjs.com/package/ts-proto/v/1.169.1) - [GitHub release](https://github.com/stephenh/ts-proto/releases/tag/v1.169.1) - `v1.169.1` Your **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:

Hi @adsau59 , this is not entirely surprising, as the `outputTypeRegistry` and `importSuffix` features were written at different times / by different contributors. If you include more context what specific...

> I am not sure what exactly what you want me to do Ah yeah; the readme describes in ts-proto [here](https://github.com/stephenh/ts-proto#development) but the basic gist is that `parameters.txt` is what...

@dasco144 ah yeah! That would be great! I thought this would be a quick PR to update, but then the build checks didn't immediately pass, for a reason I couldn't...

@dasco144 for some reason rebuilding my `protoc` service image made my local machine suddenly start matching the CI output. ...I went down a rabbit hole thinking this was related to...

This is the code that generates the index file: https://github.com/stephenh/ts-proto/blob/main/src/utils.ts#L47 I didn't write it ... I dunno, maybe each invocation of `protoc` is sending us a different order of the...

Oh shoot... @dasco144 that's a great find... So, seems like this is a synthetic problem created by the ~naive `codegen.sh` approach i.e.: * This directory has two `*.proto` files *...

Well, took awhile to get to, but I finally re-did this PR in #1050, but following up on the idea of "maybe the *.bin approach has outlived its usefulness". Now...

Hi @JakeCooper ; sorry for the late reply! Hm...it's been awhile since I've thought about this, but I wouldn't be surprised if the issue is that `Timestamp` is fundamentally a...

Hi @incompletude , sorry, I think I need to close this out, b/c there just is not a way to do it with proto behavior. I was thinking that you...