+1 (binding), checked:

- Checksums
- Signature
- Source matches tag
- No binaries
- Licence
- Build and tests from source
- npm package matches source build

Best regards,
Wei Lee



On Wednesday, November 11th, 2026 at 3:06 PM, Amogh Desai via dev 
<[email protected]> wrote:

> +1 binding.
> 
> Validated:
> 
> - SHA-512 checksum matches (shasum -a 512 -c)
> - GPG signature is good, key is in KEYS
> - Source tarball matches ts-sdk/ at 499f3b0
> - The tag (979904e) changes nothing under ts-sdk/ except the version in
> package.json (1.0.0 -> 1.0.0-rc1)
> - No binary files in the source package
> - LICENSE and NOTICE present
> - Built from source with pnpm (frozen lockfile): typecheck, tests, build
> and verify:package all pass
> - Installed @apache-airflow/[email protected] from npm, registry signatures
> verify, all exports import
> 
> Thanks & Regards,
> Amogh Desai
> 
> 
> On Tue, Nov 10, 2026 at 1:42 PM Zhe-You(Jason) Liu via dev <
> [email protected]> wrote:
> 
> > +1 (non-binding)
> >
> > Checked:
> > - Source package: checksum and signature OK, contents identical to
> > 499f3b06492, LICENSE and NOTICE present, no binaries.
> > - Built from source: tests, typecheck, build and verify:package pass.
> > - npm 1.0.0-rc1: provenance points to the ts-sdk/1.0.0-rc1 tag, and the
> > package rebuilt from the tag has the same contents.
> > - Vendored schemas match Airflow 3.4.0.
> >
> > Thanks,
> > Jason
> >
> > On Tue, Nov 10, 2026 at 3:55 PM Tzu-ping Chung via dev <
> > [email protected]> wrote:
> >
> > > Hi,
> > >
> > > I would like to call a vote to release Apache Airflow TypeScript SDK
> > 1.0.0,
> > > based on release candidate 1.0.0-rc1.
> > >
> > > Changes since 1.0.0-beta2: a task that passes queue as undefined now
> > > inherits the Dag's queue, and the build no longer uses a machine-global
> > > pnpm config that created stray .pnpm-store directories.
> > >
> > > The release candidate contains the following npm package:
> > >
> > > - @apache-airflow/ts-sdk
> > >
> > > Git information:
> > >
> > > - Tag: ts-sdk/1.0.0-rc1
> > > - Commit: 979904ed6a481c272d7258e734433eaf3b3fa72b
> > > - https://github.com/apache/airflow/releases/tag/ts-sdk%2F1.0.0-rc1
> > >
> > > The source package is built from
> > 499f3b064921946129b3f69a51370de00e1179f5;
> > > the tag adds only the -rc1 version in package.json for npm.
> > >
> > > Source release, signatures and checksums:
> > > https://dist.apache.org/repos/dist/dev/airflow/ts-sdk/1.0.0-rc1/
> > >
> > > Convenience binary (published on npm under the rc dist-tag):
> > > https://www.npmjs.com/package/@apache-airflow/ts-sdk/v/1.0.0-rc1
> > >
> > > To try the release candidate in a project:
> > >
> > > npm install @apache-airflow/[email protected]
> > >
> > > KEYS file (public keys used to sign the release):
> > > https://downloads.apache.org/airflow/KEYS
> > >
> > > Please review and vote. The vote will remain open for at least 72 hours,
> > > until 2026-11-13 08:00 UTC, or until the necessary number of binding
> > votes
> > > is reached.
> > >
> > > [ ] +1 Release this package as Apache Airflow TypeScript SDK 1.0.0
> > > [ ] +0 No opinion
> > > [ ] -1 Do not release, because ...
> > >
> > > Only votes from Airflow PMC members are binding, but everyone is welcome
> > > and encouraged to test the release and vote.
> > >
> > > The verification process can be found in the main repository. This
> > > currently reused Java SDK's verification guide; the section will be moved
> > > to a better location later.
> > >
> > >
> > https://github.com/apache/airflow/blob/main/java-sdk/DEVELOPMENT.md#verifying-a-release
> > >
> > > For more details on ASF release verification, see:
> > > https://www.apache.org/info/verification.html
> > >
> > > Best,
> > > TP
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to