Don't require that webdriver and geckodriver crates match the crates.io released version
Categories
(Testing :: geckodriver, defect, P1)
Tracking
(firefox-esr91 unaffected, firefox-esr102 unaffected, firefox102 unaffected, firefox103 wontfix, firefox104 fixed)
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox-esr102 | --- | unaffected |
firefox102 | --- | unaffected |
firefox103 | --- | wontfix |
firefox104 | --- | fixed |
People
(Reporter: jgraham, Assigned: jgraham)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [webdriver:m4][webdriver:external])
Attachments
(1 file)
This interferes with our ability to make new releases, particuarly with geckodriver where we need the upload to match the released binary which is itself build on mozilla-central. We should still publish audit information for these crates as part of the release process.
Assignee | ||
Comment 1•3 years ago
|
||
This requirement meant that we had to publish the crates on crates.io
before they reached autoland. This didn't work well for the
geckodriver release process, since the binary releases are built on
mozilla-central, and needing to pre-upload the crates made it
impossible to guarantee that the binary release matches the uploaded
version.
Instead, add a step to the release docs to update this information.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Note that this has been regressed by bug 1776096 in Firefox 103.
Comment 3•3 years ago
|
||
Updated•3 years ago
|
Comment 6•3 years ago
|
||
The patch landed in nightly and beta is affected.
:jgraham, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox103
towontfix
.
For more information, please visit auto_nag documentation.
Assignee | ||
Updated•3 years ago
|
Comment 7•3 years ago
|
||
Note that we only release off from mozilla-central. As such older releases won't need an uplift.
Updated•7 months ago
|
Description
•