Commit eeee5dab authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

HEPTAPOD_CHANGELOG: adopted from heptapod-docker

For this too, there's no reason to restrict it to
the Docker case only.

A significant policy change is that we can't really
promise anymore that unreleased changes are available in
the latest Docker images. With source installs being more
and more important to us, and the fact that the source
version necessarily predates the Docker version, it's
become too restrictive in practice.

--HG--
branch : heptapod
parent d60646a78f6e
## Changes in Heptapod
From Heptapod 0.6.0 onwards, this changelog should be sorted first by backwards
incompatibility, then by importance.
Changes mentioned here for a future, unreleased, version are already available
in the main development branches.
They *should* also be in the `latest`
[Docker image](https://hub.docker.com/r/octobus/heptapod) or in the relevant
`x.y-stable-latest` image. In case of doubt, all Heptapod instances display
the exact revision of the main repository in the user help page.
**WARNING do NOT upgrade directly from Heptapod <= 0.8 to Heptapod >= 0.12**
Please read migration instructions in the
[installation notice](INSTALL_HEPTAPOD.md)
### Heptapod 0.8.3 (2020-02-19)
- heptapod#165: a subset of Mercurial settings from the `[heptapod]` section
can now be set with the new API `PUT` on `<project_api_url>/hgrc`, in
particular without file system access.
- heptapod#196: web hooks now include Mercurial revision information (not
tested with tags and full integrations)
- heptapod#142: the "fast-forward" merge method is now supported. Mercurial
equivalent is to publish a topic.
- heptapod#143: removed deadlock situations due to existing bookmarks if
these are not explicitely allowed (implicit push & removal)
- heptapod#198: fixed detection of failed Bitbucket imports
### Heptapod 0.8.2 (2020-02-05)
- heptapod#175: backups now carry obsolescence markers and phase information.
- heptapod#182: fixed integrations setting page that was broken for some
instances migrated from pre 0.8 version.
- heptapod#180: help page now displays base GitLab version, and on source
installs such as foss.heptapod.net, doesn't have obscure error message
that `evolve` hasn't been found
- heptapod#181: fixed Bitbucket PR imports for some source installs, and
a few other failing `hg` calls
### Heptapod 0.8.1 (2020-01-23)
- heptapod#167. heptapod#169, heptapod#166: robustness for special cases in
import of Bitbucket Pull Requests
- heptapod#156: it is now possible to have a low privilege Bitbucket SSO
configuration together with a more privileged one at the same time
- heptapod#72: user and project information also available as environment
variables for external hooks in HTTP case
- heptapod#80: removed button/link to resolve conflict from the web UI
- heptapod#28: bare minimum update to mention Mercurial on
help page about merging from command line
- heptapod#3: removed creation of branches and merge requests from an issue
(not Mercurial ready).
- heptapod#133: fixes for forward slashes in topics and branch names had not
been merged from Heptapod 0.7.1
### Heptapod 0.8.0 (2020-01-17)
#### General notes
This is a release with several data migrations, including all those from
GitLab 10.3.9 to GitLab 10.5.8. Backup before applying, and if possible try
on a testing server first.
#### Specific data migrations
- heptapod#144: removed previously used SSH key for inner pushes to auxiliary
Git repository
- heptapod#150 (related): we don't need to include `/etc/gitlab/heptapod.hgrc`
from the repositories' hgrcs, `.hg/hgrc.local` gets renamed back to
`.hg/hgrc`.
- heptapod#150 (related): we don't need to include `repos.hgrc` in
`/etc/gitlab/heptapod.hgrc`, removing that.
- heptapod#159: there's a new `vcs_type` column on the `projects` table.
Its value is `hg_git` for all previously created projects. New values will
appear in the future.
#### Changes since 0.8.0rc3
- heptapod#160, heptapod#158: made imports more robust, in particular with
Bitbucket clonebundles in a context with lots of obsmarkers
- heptapod#129: proper bypass of force pull checks, which are inner details
for `hg_git` Projects
- heptapod#142: in Merge Request settings, made explicit what the default
strategy does and that the others aren't supported
- heptapod#161: Avoid importing changesets for merged
or declined Bitbucket Pull Requests.
### Heptapod 0.8.0rc3 (2020-01-08)
- heptapod#154: Fixed awareness of GitLab about SSH pushes
- heptapod-docker#1: Fixed ownership problem of HGRC files after migration
for rc2
### Heptapod 0.8.0rc2 (2020-01-07)
- heptapod#150: Make Heptapod installable from source
- heptapod#153: Restore SSH dropdown clone option
- heptapod#151: Accept trailing slash in SSH Mercurial URLs
- heptapod#144 (related): silenced user feedback about inner Git pushes
- all changes from Heptapod 0.7.1
#### Internal
- heptapod#149: factorized Mercurial access level assessments
### Heptapod 0.8.0rc1 (2019-12-25)
- heptapod#11: SSH support
- heptapod#116: GitLab 10.5.8
- heptapod#144: fire GitLab pre-receive hook directly from Mercurial
- heptapod#127: better branching strategy for the Heptapod project itself
### Heptapod 0.7.1 (2020-01-07)
- heptapod#106: importing Bitbucket Pull Requests originating from forks.
- heptapod#133: refusal/conversion of forward slashes in topic names
### Heptapod 0.7.0 (2019-12-03)
#### General notes
This is a release with several data migrations, including all those from
GitLab 10.1.7 to GitLab 10.3.9. Backup before applying, and if possible try
on a testing server first.
Users allowing drafts changesets without topics will probably need to
change the protection level of the default branch. See heptapod#129 for more
details.
Changes are listed since 0.7.0.rc1
#### Breaking changes
- heptapod!41: Heptapod Mercurial hooks have been moved to the `py-heptapod`
project, i.e, they are now part of the `heptapod.hooks` package instead of
`heptapod_hooks`.
#### Improvements and bug fixes
- heptapod#134: upon topic rename or retargeting, the previous GitLab branch
is now pruned.
- heptapod#118: minimal support for the `largefiles` extension
- heptapod#131: fixed error message for failed MR merges (regression in rc1)
### Heptapod 0.7.0rc1 (2019-11-25)
#### Breaking changes and data migrations
(at least, potentially)
- heptapod#114: GitLab base version is now 10.3.9
- heptapod#91: removed mirror-path settings from repository-local HGRCs
- heptapod#89: Mercurial version is now 5.2
- heptapod#121: post-transaction inner Git Pushes
- heptapod#73: firing of GitLab post-receive hook from Mercurial
- hg-git!22: by default, pruning Gitlab branches for closed Mercurial named
branches
- hg-git!20: pruning GitLab branches for Mercurial named branches having
only bookmarked heads
#### Changes involving data migration
(at least, potentially)
- heptapod#91: reorganisation of repositories HGRCs
- heptapod#103: support group-level HGRCs (on file system only)
- heptapod#88: GitLab base version is now 10.2.8
#### Bug fixes and backwards compatible changes
- heptapod#21: proper attribution of pushes and related actions (merge
detection, pipeline runs…)
- heptapod#112: (performance) stop scanning for repositories
- heptapod#92: better transactional properties
- heptapod#90: could not push to renamed projects
### Heptapod 0.6.3 (2019-11-25)
- heptapod#119: Robustness in case of half-rollbacked pushes, such as those due
to heptapod#92
- heptapod#122: Give end user explanations if some pushes are refused due to
protected branches and similar
- heptapod#67 (mitigation): `web.refreshinterval` can now be set in
`/etc/gitlab/heptapod.hgrc`, see also heptapod#112 for proper fix in future
version 0.7.0.
### Heptapod 0.6.2 (2019-10-30)
- heptapod#102: Bitbucket import: missing issue author information
- heptapod#105: Bitbucket import: correct import for non-fork Pull Requests
- heptapod#101: In case of multiple heads, forwarding the GitLab branch anyway,
thus preventing in particular the extreme and blocking case of named branches
not appearing after import.
### Heptapod 0.6.1 (2019-09-30)
- heptapod#93: handle closed branches properly. For backwards compatibility,
in 0.6.1, previously closed branches will not be impacted, and it's possible to
get back to the previous behaviour.
- heptapod#95: could not push by default on branches with multiple, yet closed,
heads
- heptapod#96: named branches whose head have a tag failed to be created or
updated on the GitLab side
- heptapod#94: fixed help page (/help), that was broken with 500 code since
forever
- heptapod!31: introduced HEPTAPOD_VERSION and displayed it on help page and
admin dashboard, and also removed irrelevant upgrade status badge
- hg-git#5: problems with multiple heads and branch/topic changes
- hg-git!15: fixes for import problems found while testing on the PyPy
repository
- first Docker image done from the dedicated `heptapod-docker` project.
### Heptapod 0.6.0 (2019-09-16)
#### Strongly breaking changes
- heptapod#79: now the Master project role is required to publish changesets
- non-topic draft changesets get published by default
See also the entry about Heptapod default workflow in the
[FAQ](https://heptapod.net/pages/faq.html#workflow) for more information.
#### Mildly breaking changes
- bookmarks are forbidden by default and always forbidden on topic
changesets, see also the relevant
[FAQ entry](https://heptapod.net/pages/faq.html#bookmarks).
This is only mildly breaking because they were almost always refused
in previous versions, being considered multiple heads.
- Mercurial logs by default to `/var/log/gitlab/hgserve/mercurial.log`
- heptapod#76: fixed as side effet of Mercurial not logging to `stderr`
(see above)
- internal reorganisation: hgserve WSGI wrapper and specific conf now
with the rails app, alongside `repos.hgrc`
#### Backwards compatible changes
- heptapod#60: recreated the Import from URL feature upon project creation.
- hg-git#2: multiple heads per branch support (requires explicit configuration)
- heptapod#72: user and project information available in `ui.environ` from
within Mercurial process, including hooks.
- heptapod#86: server-side obsolete heads prevented merging from the UI (should
be a rare bogus condition)
- updated base GitLab version to 10.1.7
### Heptapod 0.5.2 (2019-08-13)
- heptapod#81: fixed pushes that prune whole topics or rename them
### Heptapod 0.5.1 (2019-08-13)
- heptapod#65: a wrong exception raising that used to mask the real error
### Heptapod 0.5.0 (2019-08-12)
- heptapod#47: autodetection of Merge Requests status change (merged) upon
`hg push`, with or without rebases in the push.
- heptapod#71: fixed encoding issues in commits created by merging MRs
from GitLab
- hg-git#3: fixed crash due to the Git repository having a commit that's
unknown in the Mercurial repository (Mercurial has authority anyway)
- hgext-loggingmod#1: broken default levels for Sentry logging
### Heptapod 0.4.2 (2019-08-02)
- omnibus#8: fixed persistence of `heptapod.hgrc`
- internal reorganisation: moved Mercurial hooks into hg-git for easier
inclusion and management
### Heptapod 0.4.1 (2019-07-19)
- heptapod#59: stop crashing open Merge Request web pages if source branch has
disappeared
### Heptapod 0.4.0 (2019-07-08)
- heptapod#54: proper logging and Sentry integration for Mercurial subsystem
(`hgserve`) thanks to the `loggingmod` extension
- first `README` for the Docker image
### Heptapod 0.3.2 (2019-07-02)
- heptapod#62: unauthorized to perform used to look like a crash
- heptapod#61: final fix of anonymous operations on public repositories
(comprehensive listing read-only Mercurial wire protocol commands)
- various internal tweaks for the `hgserve` subsystem (Gunicorn)
### Heptapod 0.3.1 (2019-06-07)
- heptapod#61: partial fix for some cases of anonymous pulling on public repos
### Heptapod 0.3.0 (2019-05-24)
- first version to split HGRC into persistent and non-persistent parts
- first version to have proper tags for all components
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment