-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.9 #27
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/jamesives-github-pages-deploy-action-4.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
March 7, 2022 09:28
c9eaced
to
d731003
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.1.5
chore(deps): update jamesives/github-pages-deploy-action action to v4.2.5
Mar 7, 2022
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.2.5
chore(deps): update jamesives/github-pages-deploy-action action to v4.3.2
Apr 24, 2022
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
April 24, 2022 20:10
d731003
to
d050b64
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.3.2
chore(deps): update jamesives/github-pages-deploy-action action to v4.3.3
May 16, 2022
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
May 16, 2022 00:29
d050b64
to
fd62f80
Compare
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
September 25, 2022 12:56
fd62f80
to
32f09f1
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.3.3
chore(deps): update jamesives/github-pages-deploy-action action to v4.4.0
Sep 25, 2022
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
November 20, 2022 20:05
32f09f1
to
3856875
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.4.0
chore(deps): update jamesives/github-pages-deploy-action action to v4.4.1
Nov 20, 2022
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.4.1
chore(deps): update jamesives/github-pages-deploy-action action to v4.4.2
May 28, 2023
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
May 28, 2023 10:55
3856875
to
4e0f8ae
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.4.2
chore(deps): update jamesives/github-pages-deploy-action action to v4.4.3
Jul 12, 2023
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
July 12, 2023 04:59
4e0f8ae
to
520c6a4
Compare
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
November 28, 2023 04:21
520c6a4
to
560317a
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.4.3
chore(deps): update jamesives/github-pages-deploy-action action to v4.5.0
Nov 28, 2023
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
April 17, 2024 17:18
560317a
to
7b07ee7
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.5.0
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.0
Apr 17, 2024
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
May 18, 2024 14:15
7b07ee7
to
be756bf
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.0
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.1
May 18, 2024
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
July 5, 2024 16:07
be756bf
to
416e1a8
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.1
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.3
Jul 5, 2024
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
September 2, 2024 16:35
416e1a8
to
de993cb
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.3
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.4
Sep 2, 2024
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
September 27, 2024 16:53
de993cb
to
370f33a
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.4
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.5
Sep 27, 2024
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
September 27, 2024 18:53
370f33a
to
59998a7
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.5
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.6
Sep 27, 2024
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
September 28, 2024 13:00
59998a7
to
e11df29
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.6
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.7
Sep 28, 2024
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
September 29, 2024 15:53
e11df29
to
52a17c7
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.7
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.8
Sep 29, 2024
renovate
bot
force-pushed
the
renovate/jamesives-github-pages-deploy-action-4.x
branch
from
November 9, 2024 22:41
52a17c7
to
f1e7b06
Compare
renovate
bot
changed the title
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.8
chore(deps): update jamesives/github-pages-deploy-action action to v4.6.9
Nov 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.1.4
->v4.6.9
Release Notes
JamesIves/github-pages-deploy-action (JamesIves/github-pages-deploy-action)
v4.6.9
Compare Source
What's Changed
Dependencies 🤖
.node-version
instead of.nvmrc
for Node dependency management.Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.9
v4.6.8
Compare Source
What's Changed
Bug Fixes 🐝
origin/${branch_name} is not a commit and a branch cannot be created from it
. The action will continue to attempt to track the origin branch, but if this step fails, it will create a new untracked branch to continue the deployment from. - #1689.Testing 🧪
ie @​v4
). This was done to combat problems raised by #1697.Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.8
v4.6.7
Compare Source
What's Changed
Bug Fixes 🐝
main.js
was not found in the v4 major tag.v4.6.6
Compare Source
What's Changed
Bug Fixes 🐝
v4.6.5
Compare Source
What's Changed
What's Changed
Bug Fixes 🐝
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.5
v4.6.4
Compare Source
What's Changed
What's Changed
Bug Fixes 🐝
Build 🔧
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.4
v4.6.3
Compare Source
What's Changed
Build 🔧
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.3
v4.6.2
Compare Source
What's Changed
Dependencies 🤖
Full Changelog: JamesIves/github-pages-deploy-action@v4.6.1...v4.6.2
v4.6.1
Compare Source
What's Changed
Fixes
Dependencies
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.6.1
v4.6.0
Compare Source
What's Changed
New Contributors
Full Changelog: JamesIves/github-pages-deploy-action@v4.5.0...v4.6.0
v4.5.0
Compare Source
What's Changed
.gitignore
matches not being deployed by @sgasse in https://github.com/JamesIves/github-pages-deploy-action/pull/1459New Contributors
Full Changelog: JamesIves/github-pages-deploy-action@v4.4.3...v4.5.0
v4.4.3
Compare Source
What's Changed
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.4.3
v4.4.2
Compare Source
What's Changed
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.4.2
v4.4.1
Compare Source
What's Changed
Changelog
New Contributors
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.4.1
v4.4.0
Compare Source
What's Changed
New Contributors
Sponsors ❤️
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.4.0
v4.3.4
Compare Source
Minor Changes
branch
parameter is no longer required. It now defaults togh-pages
.New Contributors
Sponsors ❤️
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.3.4
v4.3.3
Compare Source
Changes
v4.3.2
Compare Source
Changes
v4.3.1
Compare Source
Changes
safe.directory
global directory.v4.3.0
Compare Source
Changes
force
. If set tofalse
the action will no longer force push, instead attempting 3 times to resolve rejected commits when making parallel/subsequent deployments. In a future versionfalse
will be set as the default. Massive thanks to @rossjrw for this feature addition.14
to16
.Minor Changes
v4.2.5
Compare Source
Minor Changes
v4.2.4
Compare Source
Minor Changes
v4.2.3
Compare Source
Minor Changes
v4.2.2
Compare Source
Minor Changes
JamesIves/github-pages-deploy-action@v4
if you'd like to always have the most cutting edge changes outside of using the release branch directly.v
to be consistent with other officially provided actions by GitHub. You can useJamesIves/[email protected]
for instance. Dependabot should pick up this change automatically.v4.2.1
Compare Source
Minor Changes
v4.2.0
Compare Source
Happy New Year 2022!
Minor Changes
git mv
command prior to the workflow running. (#895)single-commit
to fail when usingrepository-name
if the branch name was equal from the origin to destination. (#665)v4.1.9
Compare Source
Minor Changes
v4.1.8
Compare Source
Minor Changes
New Contributors
Full Changelog: JamesIves/github-pages-deploy-action@4.1.7...4.1.8
v4.1.7
Compare Source
Minor Changes
npm ci
instead ofnpm install
in examples by @bananer in https://github.com/JamesIves/github-pages-deploy-action/pull/934git-config-email
option again. If you wish to omit this field entirely you must now provide<>
in the field instead of an empty string. This is due to the fact that GitHub Actions defaults all undefined fields to an empty string, causing the default behavior to not work when you don't provide agit-config-email
parameter at all. You can find an example of this below.New Contributors
Full Changelog: JamesIves/github-pages-deploy-action@4.1.6...4.1.7
v4.1.6
Compare Source
Minor Changes
git-config-email
option now accepts an empty string as a valid value in a workflow. This will allow the email part of the commit signature to empty, for exampleAuthor Name <>
. You can find an example of how to utilize this below. #868v4.1.5
Compare Source
Minor Changes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.