pom for next development version not being pushed

When I run an "Artifactory Release Staging" from Jenkins, the process successfully changes the pom to the release version, performs the build (clean deploy), deploys to artifactory, tags git, changes the pom.xml in the jenkins workspace to the next development release number, but it does not push the pom including the next development release number to the git remote origin. You can see from the output below that it does a git commit with the next development version, but it does not attempt to push it. Am I doing something wrong?
-----------------------------------------------------------------------------------------------------
...
[INFO] — maven-deploy-plugin:2.7:deploy (default-deploy) @ core-proto —
[INFO] Uploading: https://accur8.artifactoryonline.com/accur8/libs-releases-local/com/accur8software/core-proto/0.9.3/core-proto-0.9.3.jar
[INFO] Uploaded: https://accur8.artifactoryonline.com/accur8/libs-releases-local/com/accur8software/core-proto/0.9.3/core-proto-0.9.3.jar (51 KB at 104.3 KB/sec)
[INFO] Uploading: https://accur8.artifactoryonline.com/accur8/libs-releases-local/com/accur8software/core-proto/0.9.3/core-proto-0.9.3.pom
[INFO] Uploaded: https://accur8.artifactoryonline.com/accur8/libs-releases-local/com/accur8software/core-proto/0.9.3/core-proto-0.9.3.pom (3 KB at 29.9 KB/sec)
[INFO] Downloading: https://accur8.artifactoryonline.com/accur8/libs-releases-local/com/accur8software/core-proto/maven-metadata.xml
[INFO] Downloaded: https://accur8.artifactoryonline.com/accur8/libs-releases-local/com/accur8software/core-proto/maven-metadata.xml (424 B at 7.3 KB/sec)
[INFO] Uploading: https://accur8.artifactoryonline.com/accur8/libs-releases-local/com/accur8software/core-proto/maven-metadata.xml
[INFO] Uploaded: https://accur8.artifactoryonline.com/accur8/libs-releases-local/com/accur8software/core-proto/maven-metadata.xml (397 B at 6.5 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.306 s
[INFO] Finished at: 2014-12-15T15:44:16-05:00
[INFO] Final Memory: 19M/156M
[INFO] ------------------------------------------------------------------------
[JENKINS] Archiving /scratch/jenkins/workspace/msg-tools/messages-core/messages-core/pom.xml to com.accur8software/core-proto/0.9.3/core-proto-0.9.3.pom
[JENKINS] Archiving /scratch/jenkins/workspace/msg-tools/messages-core/messages-core/target/core-proto-0.9.3.jar to com.accur8software/core-proto/0.9.3/core-proto-0.9.3.jar
Sending artifact delta relative to msg-tools » messages-core » core-proto #5
Archived 2 artifacts
Archive block size is 32768
Received 0 blocks and 53947 bytes
Compression is 0.0%
Took 0.33 sec
[RELEASE] Committing release version on branch 'master'
channel stopped
> git config --get remote.origin.url # timeout=10
> git add . # timeout=10
> git commit -F /tmp/gitcommit9084791703231315486.txt # timeout=10
> git config --get remote.origin.url # timeout=10
[RELEASE] Creating tag 'v0.9.3' with message 'Tagging release version 0.9.3'
> git tag -a -f -m Tagging release version 0.9.3 v0.9.3 # timeout=10
> git config --get remote.origin.url # timeout=10
[RELEASE] Pushing branch 'master' to 'git@git.emer.is:msg-tools'
> git config --get remote.origin.url # timeout=10
> git push git@git.emer.is:msg-tools refs/heads/master
> git config --get remote.origin.url # timeout=10
[RELEASE] Pushing tag 'v0.9.3' to 'git@git.emer.is:msg-tools'
> git config --get remote.origin.url # timeout=10
> git push git@git.emer.is:msg-tools refs/tags/v0.9.3
[RELEASE] Changing POMs to next development version
[RELEASE] Committing next development version on branch 'master'
> git config --get remote.origin.url # timeout=10
> git add . # timeout=10
> git commit -F /tmp/gitcommit1082019428555934180.txt # timeout=10
Finished: SUCCESS