On crates.io by running cargo publish from the release branch. Upload them all, including the checksum files for the Linux platforms.īefore announcing the release on GitHub publish the geckodriver crate as well Individual files so the basename looks like ‘geckodriver-v%version%-%platform%’. Replacing %changeset% with the full release changeset id. Make sure to check thatĪll references can be resolved, and if not make sure to add those too.įind the signed geckodriver archives in the taskcluster index by Package when they visit the GitHub downloads section. This will highlight for end-users what changes were made in that particular Paste the raw Markdown source from CHANGES.md into the description field. Specify the “Tag version”, and select “Release” as target. Therefore start toĭraft a new release, and make the following changes: Geckodriver needs to be manually released on. Also use theĬargo-semver-checks command to validate the version change: Will fail if you missed updating a crate’s dependency. Note that running cargo update (see next step)

If they have received no changes,īump the version number in Cargo.toml based on semantic versioning rules,Īnd also update the version dependency for other in-tree crates using theĬurrently modified crate. GitHub repository when we release, we first need to publish theseĬrates in the specified order if they have had any changes in the

… marionette = īecause we need to export the geckodriver source code to the old

Bump the version number and update the support page.

Turning on Firefox tests for a new configuration.

Getting Set Up To Work On The Firefox Codebase.

Cannot find mozilla geckodriver