Skip to content

Commit

Permalink
publish new versions
Browse files Browse the repository at this point in the history
  • Loading branch information
bors[bot] authored May 23, 2022
1 parent 816c87b commit 0817a58
Show file tree
Hide file tree
Showing 4 changed files with 25 additions and 15 deletions.
9 changes: 0 additions & 9 deletions .changes/fix-airtable-filenames.md

This file was deleted.

11 changes: 11 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,16 @@
# Changelog

## \[2.3.0]

- This makes the fileNode pull `name` from the airtable metadata instead of the
remote file, because when an airtable user changes the file name, airtable does
not rename the original url. This change makes file name changes in airtable
usable in the fileNode instead of needing to download, rename, and re-upload the
file.
- [4c107f6](https://github.com/jbolda/gatsby-source-airtable/commit/4c107f63af56b7e1a3f6d54d22b840c98a638c3d) Adding change file on 2021-12-13
- [0d8c3f2](https://github.com/jbolda/gatsby-source-airtable/commit/0d8c3f2c52cb98064ccfc2852afb5d9135160c3a) Copy/pasted from the example without changing the type, oops! on 2021-12-13
- [d7200c0](https://github.com/jbolda/gatsby-source-airtable/commit/d7200c0be3c5b5896fa9d479836b8d5d33ee6b03) apply suggestions from code review on 2022-05-21

## \[2.2.1]

- Add logging statement
Expand Down
18 changes: 13 additions & 5 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"name": "gatsby-source-airtable",
"description": "Gatsby Airtable Source with Linked Nodes, Multiple Tables and File Nodes.",
"version": "2.2.1",
"version": "2.3.0",
"repository": "git@github.com:jbolda/gatsby-source-airtable.git",
"author": "Jacob Bolda <me@jacobbolda.com>",
"license": "MIT",
Expand Down

0 comments on commit 0817a58

Please sign in to comment.