A new starlark-rs release

[PhilipMetzger]

The last starlark-rs release was in 2024 by @ndmitchell. But since then a bunch of internals have changed like the heap branding work done by @JakobDegen so it'd be nice if non-fbsource users could update to that work. It'd also be nice if these PRs across both buck2 and starlark-rs could get in:

• Stricter and more complete typechecking buck2#1148
• Typecheck providers buck2#1141
• Recursive type checker buck2#1289
• feat: expose RecordType from record_type module #158
• feat: expose positional to the public api #146
• feat: expose comments to parsing without changing API #178
• feat: implement bytes type #177
• starlark: Export the RecordTypeMatcher for users in the public API buck2#1283

cc @Nero5023 and @JakobDegen since both of you recently had diffs land in starlark.

There's also this PR which needs some more discussion since it would deviate the implementation even more from the spec.

Thanks.

[thesayyn]

I was not able to get any sign of life from the maintainers, it would be nice to land these changes

[ndmitchell]

I'm hoping to land or reject some of these and make a new release

[ndmitchell]

I've made a release of 0.14. It didn't include everything requested here, in particular the typing changes are not including as they'll need to wait a little longer for someone else to review them.

[PhilipMetzger]

Thank you, since this unblocks some downstream work for me. For future releases, I think having something like facebook/buck2#753 here would also help, it'd also clarify which Meta employees are responsible for this repo (even though its likely the internal build-infra team).

[PhilipMetzger]

Sorry Neil I have another slight request, but could we get a tagged release in the repo which matches the release on crates.io?

[ndmitchell]

Tag is https://github.com/facebook/starlark-rust/releases/tag/v0.14.0

I agree having clarity over who is responsible would be useful. The answer is not me though, so I'll ask someone who is to say so.