bundle command changes phase to public and probably shouldn't

[Ethan Barnes]

In our workflow we have a build server that builds our potential fixes 
on multiple platforms. A custom extension bundles our changeset(s) up 
and sends them to the build server. When an error is found, we correct 
it locally then resubmit to the build server. This may happen several 
times before a changeset is actually pushed to the master repo.

The problem is that every time we submit to the build server, the bundle 
command makes the changes public. Thus, when attempting to correct 
errors found by the build server, the phase is always "wrong".

Is there a way to tell mercurial that bundling is not pushing?

Setting [phases] publish=False doesn't change the behaviour (and in 
fact, seems to do nothing at all AFAIK).

Using version 2.3.1, though most others in my group are using a 
non-phases version, so they haven't seen this. I thought I would try to 
figure out a solution before everyone encounters this problem.

Thanks!
Ethan

This e-mail (and any attachments) is confidential and may be privileged.  Any unauthorized use, copying, disclosure or dissemination of this communication is prohibited.  If you are not the intended recipient,  please notify the sender immediately and delete all copies of the message and its attachments.