MozPhab/Changelog

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Changelog

2.8.2

  • bug 1999231 moz-phab patch -a here with jj is too verbose (prints status after every operation)

2.8.1

  • bug 2006722 display URL for new uplift linking page after successful `moz-phab uplift`

2.8.0

  • bug 1976915 Author date is not preserved when using Jujutsu with `moz-phab patch`
  • bug 1998320 add uplift and lando indicators to diff `creationMethod`

2.7.2

  • bug 1994797 add some debug log output to `get_base_remotes`
  • bug 1994906 upgrade ruff to 0.14
  • bug 1994917 `moz-phab`'s non-`submit` subcommands improperly reject multiple mutable roots or heads with Jujutsu

2.7.1

  • bug 1976915 Author date is not preserved when using Jujutsu with `moz-phab patch`
  • bug 1994777 `moz-phab patch` opens editor with no description per change on Jujutsu in 2.7.0
  • bug 1994782 run CI on Python 3.14

2.7.0

  • bug 1988622 Require `jj` 0.33.0 and later for `moz-phab`
  • bug 1994610 make `moz-phab uplift` easier to use from automation

2.6.0

  • bug 1986011 moz-phab submit doesn't say anything about jujutsu changes in descriptionless commit (no "uncommitted changes present" block)
  • bug 1990880 add ability to pass Conduit API key via the environment
  • bug 1992043 --upstream parameter is ignored
  • bug 1992268 `moz-phab`: add typing for `Repository.{apply,format}_patch(...)`
  • bug 1993055 `moz-phab patch` on Jujutsu fails to apply patches with `Multiple mutable roots found …, unable to continue`
  • bug 1994123 moz-phab uplift throws a KeyError when trying to display a link to Lando
  • bug 1994200 `test_repo_from_args` is implemented twice

2.5.0

  • bug 1984943 Avoid mocking logger in tests
  • bug 1985819 warnings from JJ can break moz-phab
  • bug 1986774 `moz-phab` appends Phabricator revision links are with LF, even if the original revision message uses CRLF
  • bug 1988251 display a link to Lando on successful `moz-phab uplift`
  • bug 1988631 `moz-phab submit`: avoid revset syntax errors with start and end range query
  • bug 1989710 Update license metadata for PEP 639

2.4.2

  • bug 1986068 OS Architecture is not being collected by telemetry

2.4.1

  • bug 1985650 improve help messages for `git.remote` config option

2.4.0

  • bug 1595047 moz-phab submit should not block updating patches with busy/unavailable reviewers if that reviewer has already approved the patch
  • bug 1975802 Don't suggest uplift form if nothing was submitted
  • bug 1984467 `moz-phab uplift` always uses `origin` as the remote when determining remote branch

2.3.0

  • bug 1595047 moz-phab submit should not block updating patches with busy/unavailable reviewers if that reviewer has already approved the patch
  • bug 1926434 decouple Phabricator revision loading/validation from `show_commit_stack`

2.2.0

2.1.0

  • bug 1731814 `moz-phab reorg` doesn't know how to reorg a non-linear stack
  • bug 1975835 PHABRICATOR_URLS dict never matches
  • bug 1975884 --no-lint option appears to be unused
  • bug 1976913 Fix workspace support for Jujutsu
  • bug 1976915 Author date is not preserved when using Jujutsu with `moz-phab patch`

2.0.0

Version 2.0.0 adds support for the `jj` VCS, as well as a new `moz-phab abandon` command.

  • bug 1956345 Add MVP support for co-located Jujutsu/`jj` to `moz-phab`
  • bug 1964150 Support non-co-located Jujutsu/`jj` repositories with `moz-phab`
  • bug 1970907 Dependency pkg_resources is deprecated and due for removal by end of 2025
  • bug 1975234 Implement `moz-phab abandon`
  • bug 1975241 install `jj` in moz-phab CI
  • bug 1975260 `moz-phab` fails with `FileNotFoundError` when `jj` is not installed
  • bug 1975290 resolve `black` formatting issues introduced by bug 1964150

1.11.0

  • bug 1966122 moz-phab executed with firefox-autoland checked out submits all patches from local autoland branch not on upstream's firefox-main

1.10.0

  • bug 1964708 moz-phab fails to detect head for branches in a pure-git based set-up
  • bug 1966288 Add auto-PR closer on GitHub

Version 1.10.1 is identical to this release due to some release hiccups. Either version can be used interchangeably.

1.9.0

  • bug 1923371 add Python 3.13 support to CI
  • bug 1928130 add a test to enforce bug numbers in commit messages in moz-phab repo
  • bug 1958111 reduce code duplication in `moz-phab reorg` for child transactions
  • bug 1958320 moz-phab tests for Python 3.11+ are not required to pass before publishing
  • bug 1958321 bump minimum Python version to 3.9, drop 3.8 support
  • bug 1960991 `Git.map_callsign_to_unified_head` assumes a Mercurial-bookmark style remote branch
  • bug 1963801 Local VCS (hg) is different from the one defined in the repository (git) when submitting patches

1.8.1

  • bug 1926924 moz-phab creates Phabricator diffs from currently checked out commit instead of the actual commit

1.8.0

  • bug 1669295 moz-phab should be able to submit without updating the working directory
  • bug 1870284 Add type hints to moz-phab
  • bug 1883957 Newly created commits are not linked to existing stacks
  • bug 1887834 Don't mark a patch as WIP when there are reviewers assigned in phabricator
  • bug 1925410 remove `requests` dependency in `dev/release_announcement.py`

1.7.0

  • bug 1828731 `moz-phab submit` should not overwrite the existing repo for the patch
  • bug 1876182 Updating moz-phab externally-managed-environment error on ubuntu 23.04/debian 12/macOS homebrew
  • bug 1887834 Don't mark a patch as WIP when there are reviewers assigned in phabricator
  • bug 1918228 moz-phab uplift complains about missing reviewers
  • bug 1920609 add Python 3.11 and 3.12 to moz-phab CI coverage
  • bug 1920610 moz-phab mocks are not calling `assert_` methods correctly resulting in a no-op
  • bug 1924716 Allow force-submitting revision
  • bug 1924899 move functionality that inspects commits into the `Commit` object

1.6.1

  • bug 1863690 `moz-phab uplift` doesn't work for beta to esr115 uplifts in mozilla-unified

1.6.0

  • bug 1908288 moz-phab uplift rebases (all?) local branches when finished
  • bug 1913235 moz-phab is using outdated glean-sdk (which fails to build on aarch64 windows)
  • bug 1916433 Support no_comment and create_branch configuration settings for patch

1.5.3

  • bug 1915447 moz-phab's `test_package` is failing due to incorrect file naming conventions

1.5.2

  • bug 1879129 `moz-phab uplift` should be clearer that a failed uplift rebase means patches won't apply on landing
  • bug 1882575 `moz-phab submit` hanging due to the spinner
  • bug 1886548 update black to version 24.3.0 in moz-phab
  • bug 1886773 When using a git repository, `moz-phab submit HASH` excludes the specified HASH
  • bug 1915447 moz-phab's `test_package` is failing due to incorrect file naming conventions

1.5.1

  • bug 1876257 AttributeError: 'Config' object has no attribute 'name' when auto-submitting after updating moz-phab to 1.5.0

1.5.0

Highlights

  • "Depends On" is no longer added to commit messages.
  • `--check-in-needed` flag is removed.
  • The update checker logic has been fixed.

Bugs

  • bug 1529766 stop adding "Depends on" messages to Phabricator revision summaries
  • bug 1700164 Removed the "check-in-needed" option
  • bug 1706667 moz-phab stops me from updating the patch if the reviewer set their state to away
  • bug 1826125 Add a mozphab setting to change the default bookmark/branch name format for patch
  • bug 1833395 Automatic self-update appears to be broken as of 1.3.0rc0
  • bug 1833884 Add Python version and OS info to the `--version` command
  • bug 1864678 disable Windows CI for moz-phab
  • bug 1864680 drop support for Python 3.7 in `moz-phab`
  • bug 1865709 remove `importlib-metadata` from moz-phab requirements
  • bug 1868464 `moz-phab uplift` doesn't warn nor error if the expected head doesn't exist
  • bug 1870284 Add type hints to moz-phab
  • bug 1870291 use `ruff` instead of `flake8` in moz-phab
  • bug 1873754 `moz-phab uplift` uses an incorrect identifier for base commit during rebase

1.4.3

  • bug 1818383 add a link to Release Management Wiki to `moz-phab uplift --help`

1.4.2

  • bug 1822104 Leak of token when using moz-phab for external project without bug tracker

1.4.1

  • bug 1819042 Unexpected file type change (normal file -> symlink) causes `moz-phab submit` to fail with Python raise error

1.4.0

Highlights

  • Eliminate many calls to the Phabricator API from moz-phab reorg.
  • Fixes several bugs around updates to revision statuses during moz-phab reorg.
  • Adds a --no-abandon flag to moz-phab reorg to avoid abandoning revisions during reorg.

Bugs

  • bug 1626028 Can't use moz-phab reorg to drop a revision from a stack that was abandoned already
  • bug 1654837 Add an option to not abandon revisions on reorg
  • bug 1773145 When reorganizing a stack with already-accepted commits, moz-phab errors
  • bug 1806479 use proper punctuation in `moz-phab help` strings
  • bug 1809187 add type hints to `moz-phab` command files
  • bug 1809214 `moz-phab uplift --train` should take a shortname instead of callsign
  • bug 1809559 stop caching Conduit calls for repo information
  • bug 1809946 make `moz-phab reorg` use `stackGraph` instead of calls to `edge.search`
  • bug 1811019 use `all` and `any` Python builtins instead of checking for `None in list` etc

1.3.0

Highlights

  • Experimental `moz-phab uplift` command is released.
  • `moz-phab patch` now takes `--diff-id` to patch an older version of a revision.
  • Self updating mechanism is disabled on Windows as it has been broken for some time.

Bugs

  • bug 1534707 `moz-phab patch` can't download specific diff id
  • bug 1754059 add moz-phab release script to repo
  • bug 1774074 moz-phab self-update always fails with incorrect target path
  • bug 1801696 Running `install-certificate` prompts user twice if there is no existing token
  • bug 1804348 `moz-phab submit` displays escape codes instead of colors on the Windows/MSYS console
  • bug 1804764 `moz-phab self-update` should log something indicating success
  • bug 1805312 refactor `git cherry` arguments into `_cherry` function for git
  • bug 1805530 Many source code files in moz-phab are missing license headers
  • bug 1805937 un-hide `uplift` command from `moz-phab` help
  • bug 1805962 `moz-phab` self-update doesn't work on Windows
  • bug 1806160 Remove "Known Issues" comment
  • bug 1806440 fix some linting errors in the readme
  • bug 1806479 use proper punctuation in `moz-phab help` strings
  • bug 1806859 cleanup fallback flag logic
  • bug 1808378 Add type hints to `conduit.py`
  • bug 1808584 patch command has `--diff-id` and `--apply-to` as mutually exclusive
  • bug 1808778 add type hints to `config.py`
  • bug 1808779 explicitly set `should_access_file` in `Config` since it is a kwarg
  • bug 1808781 add type hints to `detect_repository.py`

1.2.2

  • bug 1799685 - add a warning when `submit` fails in fallback mode
  • bug 1799685 - remove "falling back to submit" messaging
  • bug 1799674 - migrate from `setup.py` to `pyproject.toml`
  • bug 1798751 - rework update checking to make self-update display some information
  • bug 1799556 - update Windows dev requirements and environment
  • bug 1798522 - consider Mozilla Foundation and Pocket emails as Mozilla-employees
  • bug 1798406 - fix BMO API requests by using a deepcopy when sanitizing headers

1.2.1

  • bug 1798406 - raise a `BMOAPIError` after maximum retries hitting bmo

1.2.0

  • bug 1797367 - enable ANSI colour codes on Windows
  • bug 1797864 - Fix a minor grammatical typo in moz-phab warning message
  • bug 1788719 - telemetry: make new and existing UUIDs conform to expected Glean schema
  • bug 1636343 - add retries to bmo whoami request
  • bug 1691636 - validate user's hg/git email during setup and before submit
  • bug 1784701 - Add option to create a topic rather than a bookmark
  • bug 1782619 - add retries for invalid api token inputs
  • bug 1649378 - cache frequently used cat_file method
  • bug 1649376 - cache frequently used file_size method
  • bug 1649382 - cache frequently used git2hg method
  • bug 1601023 - automatically install new api token when not present
  • bug 1740228 - provide clearer messaging when falling back to submit
  • bug 1598560 - provide clearer messaging when config is invalid
  • bug 1703872 - self upgrade with --quiet when not in DEBUG mode
  • bug 1734864 - Add command to check if API token is valid
  • bug 1779081 - don't generate hunks on empty files (hg)

1.1.0

1.1.0rc2

  • bug 1613328 Add a warning when moz-phab is used without hg/evolve
  • bug 1617906 Display useful advice when CERTIFICATE_VERIFY_FAILED is encountered
  • bug 1651898 MozPhab is failing to continue if user has empty primaryEmail field
  • bug 1676574 Glean initialisation should be explicit, not during module import
  • bug 1731811 `moz-phab reorg` seems to reset the "changes planned" attribute
  • bug 1753068 Failed landing due to incorrect diff for empty files/lines.
  • bug 1762396 move to next gen CircleCI docker images
  • bug 1762403 drop support for Python 3.6 in moz-phab
  • bug 1762438 add CI for Python 3.10

1.1.0rc1

  • bug 1689162 Help Glean products migrate to new versions of metrics.yaml/pings.yaml schemas
  • bug 1737838 Add a `moz-phab uplift` command
  • bug 1741686 Relax moz-phab dependency on python-hglib
  • bug 1748906 Upgrade black to remedy failing test
  • bug 1754057 cut a new release for `moz-phab uplift`
  • bug 1757076 `moz-phab uplift` should avoid rebase if commits are already a descendant of the destination

1.0.0

  • bug 1471687 Remove local dependency on Arcanist from new Phabricator command-line app
  • bug 1688201 `FileNotFoundError` when upgrading moz-phab on Windows
  • bug 1714646 moz-phab submits to the wrong branch if you switch between branches in the same local repository
  • bug 1718540 moz-phab submit crashes when updating a differential without commit author information
  • bug 1720931 moz-phab 1.0.0rc1 is leaking changes between revisions in stack

1.0.0rc2

  • bug 1714646 moz-phab submits to the wrong branch if you switch between branches in the same local repository
  • bug 1720931 moz-phab 1.0.0rc1 is leaking changes between revisions in stack

1.0.0rc1

  • bug 1471687 Remove local dependency on Arcanist from new Phabricator command-line app
  • bug 1688201 `FileNotFoundError` when upgrading moz-phab on Windows
  • bug 1718540 moz-phab submit crashes when updating a differential without commit author information

0.1.99

  • bug 1703882 Support opt-in pre-release functionality
  • bug 1709704 Phabricator fails to create a diff if one of the files in the list of changes is empty

0.1.98

  • bug 1701353 moz-phab incorrectly displays 'It will be submitted as "Changes Planned"
  • bug 1701722 Don't explicitly request review on new revisions

0.1.97

  • bug 1700485 Don't request plan-changes on accepted revisions
  • bug 1700179 Add --no-wip to prevent reviewerless commits being tagged as WIP

0.1.96

  • bug 1610403 Allow to submit a part of a stack as "wip"
  • bug 1685308 update glean dependency to fix moz-phab installation on !tier1
  • bug 1695847 Files containing lines with just `^L` on a line result in incorrect diffs when deleted
  • bug 1696346 Explicitly set `zip_safe` to `False` to prevent unpredictable behaviour when installing
  • bug 1696357 Upgrade glean-sdk version

0.1.95

  • bug 1543963 moz-phab doesn't accept . (period) in reviewer's name
  • bug 1675648 moz-phab incorrectly handles commits with CARRIAGE RETURNs and creates unlandable diffs
  • bug 1675793 Make it clear when an error is generated by Phabricator vs. locally
  • bug 1681005 mozphab no longer works through HTTP proxy when communicating with BMO
  • bug 1681604 Add python 3.9 to the testing matrix in CircleCI
  • bug 1686291 Add missing packages to dev-requirements
  • bug 1686297 Add support for pip-compile to generate dev-requirements.txt
  • bug 1686998 Windows tests are failing due to hard-coded line separators in test
  • bug 1690649 Fix `colorama` requirement hash in requirements file for windows builds
  • bug 1691818 Fix CircleCI requirements

0.1.94

0.1.93

0.1.92

  • bug 1673303 All commands broken with "ValueError: Didn't find any metrics [...]" in latest release 0.1.91

0.1.91

Highlights

  • Operations on Mercurial repositories should now be significantly faster
  • Submissions with unchanged commits should now be faster
  • moz-phab patch --raw now includes metadata (author, subject)

All Changes

0.1.90

  • bug 1619855 Warn about Python version < 3.6
  • bug 1645300 Do not search for parent-child relationship if single
  • bug 1641199 Reduce the number of failed tests in Windows

0.1.89

0.1.88

0.1.87

0.1.86

  • bug 1627405 Fix deletion of the source when copying to multiple targets.

0.1.85

0.1.84

0.1.83

0.1.82

0.1.81

  • bug 1623370 Fixed restarting on Windows after an automated update
  • bug 1621731 Improve performance on large HG repos

0.1.80

0.1.79

0.1.78

0.1.77

0.1.76

0.1.75

0.1.74

  • bug 1610583 Fix handling of files without trailing newlines on hg

0.1.73

  • bug 1606175 Detecting if installed with --user option fixed.
  • bug 1609207 Show the right error when trying to reorganize a split stack

0.1.71

0.1.70

  • bug 1605124 "unable to apply patch" for Python < 3.6 fixed

0.1.69

0.1.68

0.1.67

0.1.66

  • bug 1602545 MozPhab is able to submit to vanilla Phabricator instances

0.1.65

0.1.64

  • bug 1599596 Fix --no-bug for updating existing revisions using --no-arc

0.1.63

  • bug 1599184 Fix --no-bug for submitting new revisions using --no-arc

0.1.62

0.1.61

0.1.60

0.1.59

  • Windows users can again submit patches with the --no-arc option
  • bug 1591015 CRLF fix
  • bug 1591248 Fix the ~/.arcrc file mode if needed
  • bug 1593981 Do not check if Arcanist is configured when --no-arc is used.

0.1.58

0.1.57

0.1.56

  • bug 1591015 Switched off the ability to submit without Arcanist.
Retrieved from "https://wiki.mozilla.org/index.php?title=MozPhab/Changelog&oldid=1256293"