Repository navigation
Restructure repo for dual Node.js/Python packages with manual releases - #16
Merged
Merged
Conversation
… publishing Move the npm package (bin/, lib/, package.json, lockfile, example-actor/ and its README) into javascript/, mirroring the existing python/ directory, and replace the root README with a short summary that links to the two runtime-specific READMEs. publish.yml now runs from javascript/ and publishes via npm Trusted Publishing (OIDC): id-token: write, Node 24 with npm >= 11.5.1, no NPM_TOKEN and no GitHub environment (the trusted publisher on npmjs.com is configured with only the repository and the workflow file name). package.json's repository, bugs and homepage URLs move from Pijukatel to apify, with repository.directory set - npm requires repository.url to match the publishing repository exactly. pyproject.toml gets Apify as author plus Repository and Issue Tracker URLs. README cross-links use absolute GitHub URLs so they resolve on npmjs.com and pypi.org as well as on GitHub. Verified locally from the new layout: node --check on all sources, both workflow smoke tests, npm pack --dry-run (same 5 files as before). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W7hhx4kHxbYsuC6QmAB9yS
…elease itself publish.yml is now started with workflow_dispatch on master instead of reacting to pushed v* tags. It publishes the version javascript/package.json carries, then pushes the annotated vX.Y.Z tag and creates the GitHub release with generated notes (starting from the previous v* tag, so the Python py-v* tags do not leak into the range). Tags and releases are no longer created by hand. Guards: the run must be on master, the version must not be on npm yet (checked against the registry's versions list, so a registry error fails the job instead of passing as "new"), and the tag must not exist yet, so a re-run after a failure is safe. A concurrency group prevents two releases from racing. The publish job gets contents: write for the tag and release. READMEs describe the new flow: bump the version in a PR, then run the workflow. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W7hhx4kHxbYsuC6QmAB9yS
…release itself publish_to_pypi.yml now mirrors publish.yml: started with workflow_dispatch on master only, it publishes the version python/pyproject.toml carries, then pushes the annotated py-vX.Y.Z tag and creates the GitHub release with generated notes (starting from the previous py-v* tag, so npm's v* tags do not leak into the range). The py-v* tag trigger is gone; tags and releases are no longer created by hand. Guards: the run must be on master, pyproject.toml and __init__.__version__ must agree, the version must not be on PyPI yet (checked against PyPI's releases list with curl -f, so a network error fails the job instead of passing as "new"), and the tag must not exist yet, so a re-run after a failure is safe. A concurrency group prevents two releases from racing. The publish job gets contents: write for the tag and release. READMEs describe the new flow for both packages. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W7hhx4kHxbYsuC6QmAB9yS
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W7hhx4kHxbYsuC6QmAB9yS
…le screenshot Adds an intro that positions the package as an in-browser Python debugger for the Apify platform, plus a screenshot of the debugger UI in the Live view tab of a run (python/docs/apify-console-live-view.png, referenced by its raw GitHub URL so it also renders on pypi.org). The image file itself is added separately. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W7hhx4kHxbYsuC6QmAB9yS
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W7hhx4kHxbYsuC6QmAB9yS
…5, PyPI 0.1.2 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W7hhx4kHxbYsuC6QmAB9yS
Pijukatel
marked this pull request as ready for review
September 18, 2026 12:14
apify-service-account
added
the
t-tooling
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
javascript/next topython/; the root README becomes a short overview linking to the two runtime READMEs.master, publish via npm/PyPI Trusted Publishing (OIDC, no secrets), and then create thevX.Y.Z/py-vX.Y.Ztag and GitHub release themselves; they refuse already-published versions or existing tags.Pijukateltoapify(repository.url+directoryin package.json, which npm trusted publishing requires; Apify as author in pyproject.toml).