Repeatable migration with version incorrectly detected as versioned migration

[mtcremin]

What version of Flyway are you using?

4.1.2

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)

Command-line

What database are you using (type & version)?

MS SQL 2016

What operating system are you using?

Windows 10

What did you do?

(Please include the content causing the issue, any relevant configuration settings, and the command you ran)
Files:
R1.1__create_test2.sql
V1.2__create_test4.sql
R__create_test1.sql
V__create_test3.sql

Commands:

flyway migrate
update files:
R__create_test1.sql
V__create_test3.sql

flyway info
+---------+------------------------------+---------------------+---------+
| Version | Description | Installed on | State |
+---------+------------------------------+---------------------+---------+
| | << Flyway Schema Creation >> | 2017-04-03 14:57:02 | Success |
| 1.1 | create test2 | 2017-04-03 14:57:02 | Success |
| 1.2 | create test4 | 2017-04-03 14:57:02 | Success |
| | create test1 | 2017-04-03 14:57:02 | Outdate |
| | create test3 | 2017-04-03 14:57:02 | Outdate |
| | create test1 | | Pending |
| | create test3 | | Pending |
+---------+------------------------------+---------------------+---------+

What did you expect to see?

ERROR: V__create_test3.sql - Invalid version missing version number
ERROR: R1.1__create_test2.sql - Invalid repeatable cannot contain version number

What did you see instead?

R and V files are treated the similarly. If an R file has a version (R1.1__) it is treated as a version file. When a V file does not include a version (V__) it is treated as a repeatable file.

Is this expected?