commit | 4abc9c83a81090170b0aa8b8e3a8f3af812e36c8 | [log] [tgz] |
---|---|---|
author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Fri Sep 08 20:17:57 2023 +0900 |
committer | GitHub <noreply@github.com> | Fri Sep 08 20:17:57 2023 +0900 |
tree | ae25cff31fd9b2faec3d1659596cfa64003c8543 | |
parent | 285ef67ecede0a0dd171593e92cec21046153905 [diff] |
Bump actions/setup-python from 2 to 4 (#403) Bumps [actions/setup-python](https://github.com/actions/setup-python) from 2 to 4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/actions/setup-python/releases">actions/setup-python's releases</a>.</em></p> <blockquote> <h2>v4.0.0</h2> <h3>What's Changed</h3> <ul> <li>Support for <code>python-version-file</code> input: <a href="https://redirect.github.com/actions/setup-python/issues/336">#336</a></li> </ul> <p>Example of usage:</p> <pre lang="yaml"><code>- uses: actions/setup-python@v4 with: python-version-file: '.python-version' # Read python version from a file - run: python my_script.py </code></pre> <p>There is no default python version for this <code>setup-python</code> major version, the action requires to specify either <code>python-version</code> input or <code>python-version-file</code> input. If the <code>python-version</code> input is not specified the action will try to read required version from file from <code>python-version-file</code> input.</p> <ul> <li>Use pypyX.Y for PyPy <code>python-version</code> input: <a href="https://redirect.github.com/actions/setup-python/issues/349">#349</a></li> </ul> <p>Example of usage:</p> <pre lang="yaml"><code>- uses: actions/setup-python@v4 with: python-version: 'pypy3.9' # pypy-X.Y kept for backward compatibility - run: python my_script.py </code></pre> <ul> <li> <p><code>RUNNER_TOOL_CACHE</code> environment variable is equal <code>AGENT_TOOLSDIRECTORY</code>: <a href="https://redirect.github.com/actions/setup-python/issues/338">#338</a></p> </li> <li> <p>Bugfix: create missing <code>pypyX.Y</code> symlinks: <a href="https://redirect.github.com/actions/setup-python/issues/347">#347</a></p> </li> <li> <p><code>PKG_CONFIG_PATH</code> environment variable: <a href="https://redirect.github.com/actions/setup-python/issues/400">#400</a></p> </li> <li> <p>Added <code>python-path</code> output: <a href="https://redirect.github.com/actions/setup-python/issues/405">#405</a> <code>python-path</code> output contains Python executable path.</p> </li> <li> <p>Updated <code>zeit/ncc</code> to <code>vercel/ncc</code> package: <a href="https://redirect.github.com/actions/setup-python/issues/393">#393</a></p> </li> <li> <p>Bugfix: fixed output for prerelease version of poetry: <a href="https://redirect.github.com/actions/setup-python/issues/409">#409</a></p> </li> <li> <p>Made <code>pythonLocation</code> environment variable consistent for Python and PyPy: <a href="https://redirect.github.com/actions/setup-python/issues/418">#418</a></p> </li> <li> <p>Bugfix for <code>3.x-dev</code> syntax: <a href="https://redirect.github.com/actions/setup-python/issues/417">#417</a></p> </li> <li> <p>Other improvements: <a href="https://redirect.github.com/actions/setup-python/issues/318">#318</a> <a href="https://redirect.github.com/actions/setup-python/issues/396">#396</a> <a href="https://redirect.github.com/actions/setup-python/issues/384">#384</a> <a href="https://redirect.github.com/actions/setup-python/issues/387">#387</a> <a href="https://redirect.github.com/actions/setup-python/issues/388">#388</a></p> </li> </ul> <h2>v3.1.4</h2> <h2>What's Changed</h2> <p>In the scope of this patch release, the warning for deprecating Python 2.x was added in <a href="https://redirect.github.com/actions/setup-python/pull/674">actions/setup-python#674</a> by <a href="https://github.com/dmitry-shibanov"><code>@dmitry-shibanov</code></a></p> <p>For more information, check out <a href="https://redirect.github.com/actions/setup-python/issues/672">actions/setup-python#672</a></p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/actions/setup-python/commit/61a6322f88396a6271a6ee3565807d608ecaddd1"><code>61a6322</code></a> Fix typos found by codespell (<a href="https://redirect.github.com/actions/setup-python/issues/650">#650</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/ea5b57fccc93aea0d77e6225efa19adaec3fce0d"><code>ea5b57f</code></a> Bump semver from 7.3.8 to 7.5.2 (<a href="https://redirect.github.com/actions/setup-python/issues/692">#692</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/014d32a83013b439dd2a147051d855831576a3ef"><code>014d32a</code></a> Bump tough-cookie and <code>@azure/ms-rest-js</code> (<a href="https://redirect.github.com/actions/setup-python/issues/697">#697</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/c16c4b8d1828103eda022b2cade091238fe08311"><code>c16c4b8</code></a> Fix pipenv jobs (<a href="https://redirect.github.com/actions/setup-python/issues/699">#699</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/0d5da6a89a3aa5b4dbd48e38b0c9d678b0caa0e5"><code>0d5da6a</code></a> Read python version from pyproject.toml (fix <a href="https://redirect.github.com/actions/setup-python/issues/542">#542</a>) (<a href="https://redirect.github.com/actions/setup-python/issues/669">#669</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/3f824b7ca6388f5e27e362d31352e6456c8e3bfb"><code>3f824b7</code></a> remove python 2.7 from the tests (<a href="https://redirect.github.com/actions/setup-python/issues/687">#687</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/bd6b4b6205c4dbad673328db7b31b7fab9e241c0"><code>bd6b4b6</code></a> Add warning for python 2.7 (<a href="https://redirect.github.com/actions/setup-python/issues/673">#673</a>)</li> <li><a href="https://github.com/actions/setup-python/commit/0cbcb9a3d7c0b228a2c4fbde82b6e8855233cd92"><code>0cbcb9a</code></a> Merge pull request <a href="https://redirect.github.com/actions/setup-python/issues/668">#668</a> from akv-platform/disallow-implicit-dependencies</li> <li><a href="https://github.com/actions/setup-python/commit/669664dac1a46a4bb872089e1a90e4ad5dc232a6"><code>669664d</code></a> Merge branch 'tool-config-auto-update' into disallow-implicit-dependencies</li> <li><a href="https://github.com/actions/setup-python/commit/9cbf792a3cbbd9c37749da21d3b171b927451bb0"><code>9cbf792</code></a> Update configuration files</li> <li>Additional commits viewable in <a href="https://github.com/actions/setup-python/compare/v2...v4">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=actions/setup-python&package-manager=github_actions&previous-version=2&new-version=4)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Jekyll is used to generate HTML files from the Markdown + templates in this repository. The built version of the site is kept on the asf-site
branch, which gets deployed to https://arrow.apache.org.
To add a blog post, create a new markdown file in the _posts
directory, following the model of existing posts. In the front matter, you should specify an “author”. This should be your Apache ID if you have one, or it can just be your name. To add additional metadata about yourself (GitHub ID, website), add yourself to _data/contributors.yml
. This object is keyed by apacheId
, so use that as the author
in your post. (It doesn't matter if the ID actually exists in the ASF; all metadata is local to this project.)
With a recent version of Ruby (i.e. one that does not have an End-Of-Life (EOL) status) installed, run the following commands to install Jekyll.
gem install bundler
bundle install
We also need Node.JS to use webpack for maintaining dependent JavaScript and CSS libraries.
We can install webpack and dependent JavaScript and CSS libraries automatically by following command lines to preview or build the site. So we just need to install Node.JS here.
Run the following and open http://localhost:4000/ to preview generated site locally:
bundle exec rake
On a commit to the main
branch of apache/arrow-site
, the rendered static site will be published to the asf-site
branch using GitHub Actions.
When implementing changes to the website on a fork, the GitHub Actions workflow behaves differently.
On a commit to the main
branch, the rendered static site will be published to a branch named gh-pages
(rather than asf-site
). If it doesn't already exist, a gh-pages
branch will be automatically created by the GitHub Actions workflow when it succeeds.
The gh-pages branch is intended to be used with GitHub Pages. Deploying changes on the gh-pages
branch to GitHub Pages is a useful way to preview changes to the website. It can also be a helpful way to share changes that are still in progress with others, since they can easily view them by navigating to the GitHub Pages URL in their web browser.
For the changes on the gh-pages
branch to be deployed to GitHub Pages, the Source branch for GitHub Pages deployment must be set to gh-pages
in the repository Settings of your fork (by default, the Source branch should be set to asf-site
). Instructions on how to configure the Source branch can be found in the GitHub Pages documentation.
FYI: We can also generate the site for https://arrow.apache.org/ to _site/
locally by the following command line:
JEKYLL_ENV=production bundle exec rake generate
To update the documentation, you can run the script ./dev/gen_apidocs.sh
in the apache/arrow
repository. This script will run the code documentation tools in a fixed environment.
First, build Apache Arrow C++ and Apache Arrow GLib. This assumes that you have checkouts your forks of arrow
and arrow-site
alongside each other in your file system.
mkdir -p ../cpp/build cd ../cpp/build cmake .. -DCMAKE_BUILD_TYPE=debug make cd ../../c_glib ./autogen.sh ./configure \ --with-arrow-cpp-build-dir=$PWD/../cpp/build \ --with-arrow-cpp-build-type=debug \ --enable-gtk-doc LD_LIBRARY_PATH=$PWD/../cpp/build/debug make GTK_DOC_V_XREF=": " rsync -r doc/reference/html/ ../../arrow-site/asf-site/docs/c_glib/
cd ../js npm run doc rsync -r doc/ ../../arrow-site/asf-site/docs/js
Then add/commit/push from the asf-site/
git checkout.
If you don't wish to change or install ruby
and nodejs
locally, you can use docker to build and preview the site with a command like:
docker run -v `pwd`:/arrow-site -p 4000:4000 -it ruby bash cd arrow-site apt-get update apt-get install -y npm gem install bundler bundle install # Serve using local container address bundle exec rake HOST=0.0.0.0
Then open http://locahost:4000 locally